React Native EXPO Apple upload fail [on hold]
I created the app through Expo.
I uploaded the ipa through the Application Loader, and it was rejected as the message below.
What is the problem?
This bundle is invalid - The Info.plist file for /Payload/ExpoKitApp.app/FacebookSDKStrings.bundle is missing or could not be read.
Invalid Bundle - The bundle at ‘/Payload/ExpoKitApp.app/FacebookSDKStrings.bundle’ does not contain a bundle executable.
reactjs react-native expo
Post is related to a rapidly changing event.
put on hold as off-topic by Bhargav Rao♦ 1 min ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Bhargav Rao
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I created the app through Expo.
I uploaded the ipa through the Application Loader, and it was rejected as the message below.
What is the problem?
This bundle is invalid - The Info.plist file for /Payload/ExpoKitApp.app/FacebookSDKStrings.bundle is missing or could not be read.
Invalid Bundle - The bundle at ‘/Payload/ExpoKitApp.app/FacebookSDKStrings.bundle’ does not contain a bundle executable.
reactjs react-native expo
Post is related to a rapidly changing event.
put on hold as off-topic by Bhargav Rao♦ 1 min ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Bhargav Rao
If this question can be reworded to fit the rules in the help center, please edit the question.
1
I'm having the exact same problem and my app doesn't use React Native EXPO. I think there is an issue with AppStoreConnect at the moment. This is not related to Expo. It may be a general issue. I tried uploading the bundle many times. The same exact app yesterday was accepted just fine, and today I have this problem. I changed no code at all, so this is 100% an issue on the Apple side.
– Axy
1 hour ago
add a comment |
I created the app through Expo.
I uploaded the ipa through the Application Loader, and it was rejected as the message below.
What is the problem?
This bundle is invalid - The Info.plist file for /Payload/ExpoKitApp.app/FacebookSDKStrings.bundle is missing or could not be read.
Invalid Bundle - The bundle at ‘/Payload/ExpoKitApp.app/FacebookSDKStrings.bundle’ does not contain a bundle executable.
reactjs react-native expo
I created the app through Expo.
I uploaded the ipa through the Application Loader, and it was rejected as the message below.
What is the problem?
This bundle is invalid - The Info.plist file for /Payload/ExpoKitApp.app/FacebookSDKStrings.bundle is missing or could not be read.
Invalid Bundle - The bundle at ‘/Payload/ExpoKitApp.app/FacebookSDKStrings.bundle’ does not contain a bundle executable.
reactjs react-native expo
reactjs react-native expo
asked 2 hours ago
Kihyun AnKihyun An
727
727
Post is related to a rapidly changing event.
Post is related to a rapidly changing event.
put on hold as off-topic by Bhargav Rao♦ 1 min ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Bhargav Rao
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by Bhargav Rao♦ 1 min ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Bhargav Rao
If this question can be reworded to fit the rules in the help center, please edit the question.
1
I'm having the exact same problem and my app doesn't use React Native EXPO. I think there is an issue with AppStoreConnect at the moment. This is not related to Expo. It may be a general issue. I tried uploading the bundle many times. The same exact app yesterday was accepted just fine, and today I have this problem. I changed no code at all, so this is 100% an issue on the Apple side.
– Axy
1 hour ago
add a comment |
1
I'm having the exact same problem and my app doesn't use React Native EXPO. I think there is an issue with AppStoreConnect at the moment. This is not related to Expo. It may be a general issue. I tried uploading the bundle many times. The same exact app yesterday was accepted just fine, and today I have this problem. I changed no code at all, so this is 100% an issue on the Apple side.
– Axy
1 hour ago
1
1
I'm having the exact same problem and my app doesn't use React Native EXPO. I think there is an issue with AppStoreConnect at the moment. This is not related to Expo. It may be a general issue. I tried uploading the bundle many times. The same exact app yesterday was accepted just fine, and today I have this problem. I changed no code at all, so this is 100% an issue on the Apple side.
– Axy
1 hour ago
I'm having the exact same problem and my app doesn't use React Native EXPO. I think there is an issue with AppStoreConnect at the moment. This is not related to Expo. It may be a general issue. I tried uploading the bundle many times. The same exact app yesterday was accepted just fine, and today I have this problem. I changed no code at all, so this is 100% an issue on the Apple side.
– Axy
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
The issue is in the AppStoreConnect, as @Axy said, yesterday upload was fine, and I try to do today, I receive same error related Facebook bundle, nothing I've changed in my end,
It is an Apple related issue.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The issue is in the AppStoreConnect, as @Axy said, yesterday upload was fine, and I try to do today, I receive same error related Facebook bundle, nothing I've changed in my end,
It is an Apple related issue.
add a comment |
The issue is in the AppStoreConnect, as @Axy said, yesterday upload was fine, and I try to do today, I receive same error related Facebook bundle, nothing I've changed in my end,
It is an Apple related issue.
add a comment |
The issue is in the AppStoreConnect, as @Axy said, yesterday upload was fine, and I try to do today, I receive same error related Facebook bundle, nothing I've changed in my end,
It is an Apple related issue.
The issue is in the AppStoreConnect, as @Axy said, yesterday upload was fine, and I try to do today, I receive same error related Facebook bundle, nothing I've changed in my end,
It is an Apple related issue.
edited 2 mins ago
Bhargav Rao♦
30.5k2091112
30.5k2091112
answered 1 hour ago
ardy wongsoardy wongso
785
785
add a comment |
add a comment |
1
I'm having the exact same problem and my app doesn't use React Native EXPO. I think there is an issue with AppStoreConnect at the moment. This is not related to Expo. It may be a general issue. I tried uploading the bundle many times. The same exact app yesterday was accepted just fine, and today I have this problem. I changed no code at all, so this is 100% an issue on the Apple side.
– Axy
1 hour ago