-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expo-camera work well on Expo Client, but it make crash app when I build ios standalone app #5160
Comments
Hey @truyet , I just tested this on a blank |
I saw my app crashing twice (today and yesterday). both when using the camera. Don't know if its related to this issue but i've attached a crash report. iPhone 7 - iOS 13 - standalone SDK34 (managed) |
iOS 13 is in beta, so it could be related to that. If so, we appreciate you bringing this up. @truyet is this on iOS 13 for you as well? |
@cruzach , I run on IOS 12.4 device |
I have the same issue on iOS 12.4 and SDK 34. It crashes every time I open the camera on the standalone app, expo client works well. |
Same here ! |
Looks like more and more people are running into this. Same there, camera crashes on standalone app but works perfectly on Expo. iOS 12.4. SDK 34. |
Crashes on iOS Standalone and Custom iOS Expo client with SDK34. @cruzach @sjchmiela @tsapeta . Perhaps due to deprecating File System for expo-file-system ? |
We are also experience this problem with SDK34 (managed). No problem in the expo client but standalone build crashes on iPhone X ( IOS 12.3.1). When I open the camera it will prompt for access to the camera, once I give it access it will crash. It will crash right away if I try to start the app again. But if I go to my settings on my phone, remove the access to the camera and try to start the app again, it will work. It will also not crash if I say no to giving the app access to the camera right away. When not giving it access to the camera I can also open my image library, choose a picture from there and proceed. So the issues seems to be directly related to the camera in some way. |
me too sdk34 ios only. |
We are also experiencing the same issue. iOS 12.4, SDK 34. |
Hey guys, @sweebee's crash report was helpful and I was able to find a bug in
I have put up a PR which should fix the issue, we'll port it to builders as soon as possible, sorry for the trouble! If anyone has any more crash reports they would be helpful since we would be able to ensure this is the real cause of all the problems. |
Somehow those crash logs are less explicit than @sweebee's (there are no method names), I guess we will have to wait for the deploy to see if that fix worked. |
My bug report comes from the expo barcode scanner not from the expo camera. Don't know if your pull request also fixes the issue in the normal camera? I'm not using the camera for barcodes since it has also a bug on iOS: #5092 |
Here's the trace from a crash on a build from ~4 hours ago that I just loaded up through Testflight.
Notably: we've only passed |
Anyone find a work around in the meanwhile? |
Thank you, @dominic, for providing the stack trace, it has been really helpful! We will fix the problem as soon as possible. 🙂 |
…5183) # Why Should fix #5160. # How I inspected crash log (#5160 (comment)) and found that it points to this line to this error. Now the code will ensure that the value it wants to send to JS is not nil. # Test Plan I haven't executed any tests, Expo client compiled.
#5194) # Why Potential fix for #5160. # How Latest obtained [crash stack trace](#5160 (comment)) suggests it's actually the Firebase what is crashing. This could happen either because we don't include proper `GoogleService-Info.plist` inside shell app or due to some other problem. This should prevent crashing when initializing face detector fails. # Test Plan I looked at previous revision of `EXFaceDetectorManager.m` and creating face detector was happening inside `try-catch`: https://github.com/expo/expo/blob/1da2f1891ab578f1f442a5ec069186f2f085cd12/packages/expo-face-detector/ios/EXFaceDetector/EXFaceDetectorManager.m#L103-L109
…5183) # Why Should fix #5160. # How I inspected crash log (#5160 (comment)) and found that it points to this line to this error. Now the code will ensure that the value it wants to send to JS is not nil. # Test Plan I haven't executed any tests, Expo client compiled.
#5194) # Why Potential fix for #5160. # How Latest obtained [crash stack trace](#5160 (comment)) suggests it's actually the Firebase what is crashing. This could happen either because we don't include proper `GoogleService-Info.plist` inside shell app or due to some other problem. This should prevent crashing when initializing face detector fails. # Test Plan I looked at previous revision of `EXFaceDetectorManager.m` and creating face detector was happening inside `try-catch`: https://github.com/expo/expo/blob/1da2f1891ab578f1f442a5ec069186f2f085cd12/packages/expo-face-detector/ios/EXFaceDetector/EXFaceDetectorManager.m#L103-L109
@sjchmiela Will this change be picked up if I build a new version of my app via Expo's servers, or do we need to wait for the release of a new version of |
@asttel re: symbols, I pulled this off a Testflight app on a device I'd set up for development via Xcode. It looks like all Testflight/App Store reported crashes should be symbolicated correctly per Apple's technical note (and you can re-symbolicate one manually via those instructions as well, though it looks a little complicated). |
Seems to still crash for me on a TestFlight build from ~an hour ago. Not sure how to get crash logs (I think you need iOS 13 for that). Could it still be happening because I didn't reinstall my node modules before building? Seems like I also built on expo-cli 3.0.8, while the latest is 3.0.9. Going to update and try again. Update: still crashing on new testflight build after updating expo-cli (3.0.9), expo (34.0.4) and expo-camera (6.0.0) |
I will let you know when the fix is deployed. Once it is, you will need to rebuild your iOS app ( |
The issue should be fixed now. Try rebuilding your apps with |
@sjchmiela looks to still be occurring with the expo custom client build |
Yeah, Expo custom client builds are yet to be fixed, on it! |
I use turtle-cli to build the ios app, does it should work now with expo 34.0.4 ? Or should I wait an expo update ? |
You will need to use just-published |
Custom Expo clients built from now on should include that fix. 🙂 |
Cheers! |
I have the same issue on Android. The log is below.
import { Camera } from 'expo-camera';
<Camera
style={styles.camera}
onBarCodeScanned={this.handleBarCodeScanned}
flashMode={torch}
ref={(cam) => {
this.camera = cam;
}}
></Camera>
[android.log](https://github.com/expo/expo/files/3490910/android.log) |
I also still have to same issue running
|
Hi @changjingli. Since your crash happens on Android, maybe it would be best to create a new issue. |
Hi @sjchmiela sorry for the last response but it still is not working with FaceDetector. Last Exception Backtrace: |
Hey, @He1nr1chK! When was the last time you have rebuilt your native app? ( |
My mistake, yes my app is ejected. Don't know how I missed that detail on the tread. Any active issues on the topic? @sjchmiela |
Try upgrading to |
Thank you! |
🐛 Bug Report
expo-camera work well on Expo Client, but it make crash app when I build ios standalone app
Environment
IOS Standalone App build
Expo CLI 3.0.6 environment info:
System:
OS: macOS 10.14.5
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.6.0 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.4 AI-183.5429.30.34.5452501
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
expo: ^34.0.3 => 34.0.3
react: 16.8.3 => 16.8.3
react-native: https://github.com/expo/react-native/archive/sdk-34.0.0.tar.gz => 0.59.8
react-navigation: ^3.11.1 => 3.11.1
npmGlobalPackages:
expo-cli: 3.0.6
Steps to Reproduce
Ask permission camera on app -> camera permission approved -> Camera tag is render and app crashed on IOS
Expected Behavior
Camera show preview
Actual Behavior
App crashed
The text was updated successfully, but these errors were encountered: