[camera] iOS crash under [FLTCam onCancelWithArguments:] #76297
Comments
|
@flutter-symbolizer-bot force ios arm64 #76297 (comment) engine#2f0af37152 |
|
crash from #76297 (comment) symbolized using symbols for (Load address missing from the report, detected heuristically: 00000001050f8000) |
|
P.S. I was on a previous version of xcode when this was built - it was |
|
@carman247 |
darshankawar
added
the
waiting for customer response
I'm currently updating to latest version of camera package |
no-response
bot
removed
the
waiting for customer response
|
Labeling this for further investigation, since there's no reproducible use case that crashes the app. |
darshankawar
added
a: release
Will do :) |
|
The crash message is different, but when I take a picture of the camera, the flash fires and iOS crashes. Is it the same problem? flutter 1.22.6 ----------------flutter doctor -v -------------- [✓] Flutter (Channel stable, 1.22.6, on macOS 11.2.1 20D74 darwin-arm, locale ja-JP) [✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3) [✓] Xcode - develop for iOS and macOS (Xcode 12.4) [✓] Android Studio (version 4.1) [!] VS Code (version 1.53.2) [✓] Connected device (1 available) -------------crash repo---------------- EXC_BAD_ACCESS: isEqual: > UTF8String > ----------------pubspec.yaml-------------- name: tflite_demo version: 1.0.0+1 environment: dependencies: cupertino_icons: ^0.1.2 dev_dependencies: flutter_native_splash: flutter: |
|
sorry. |
Any news? |
Hi, yes! Sorry for late response. I upgraded from camera: ^0.5.6 to 0.6.0 and it seems to have fixed the problem. I wasn't able to update to the latest version, due to some weird behaviour with orientation on iOS but that's ok and not related to this issue. |
|
The same issue is logged in Crashlytics from our app: List of dependencies from pubspec.yml of our app:flutter doctor -vI don't have the reproducible steps. |
|
update: I tried to pick the image from the camera and working fine. |
|
@darshankawar is it similar to #79335? |
stuartmorgan
changed the title
|
As the OP confirmed that the issue doesn't occur anymore after upgrading to version 0.6.0 (coming from 0.5.6) I think we can close this issue. The issue mentioned by @deepak786 is not related to the camera plugin (as he doesn't use the camera plugin in his project) and seems (although not directly clear from the stack trace) related to the image_picker which is a separate plugin and is therefore unrelated. @deepak786 if you are still experiencing this issue with the image_picker plugin, please create a new issue. @stuartmorgan do you agree with closing the issue? |
|
@mvanbeusekom I think for me the issue was #79335 which is already solved. I don't have new crashes. |
|
@mvanbeusekom #76297 (comment) is the same stack, but with 0.7.0, so I'm skeptical that it's actually fixed. |
Yes I also noticed that issue, however the same user mentions in this comment that he was specifying a none existing file name that caused the crash. |
|
We shouldn't crash the entire app if someone provides an incorrect filename; if that's indeed the cause, that means we have a repro case to work from. |
|
You are right something definitely is going wrong, I will start a further investigation. |
Since 0.6.0 it is not possible anymore to supply a file name yourself when starting the camera for video or taking a picture. For everybody else it looks like this issue was fixed in 0.7.0 |
mvanbeusekom
added
the
waiting for customer response
jmagman
added this to Awaiting triage
in iOS Platform - first party plugin and package review
|
@mvanbeusekom Hi, Should this issue be kept open or can be closed ? #76297 (comment) |
|
@darshankawar I feel we can close this issue. We are unable to reproduce it after version 0.7.0 and also didn't receive any feedback from the community the problem still exists. According to this I will now close this issue. However if this issue still occurs on version 0.7.0 please let us know and provide the necessary details and we'd be happy to re-open the issue and get it solved. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
flutter-triage-bot
bot
added
the
package
I'm not quite sure what's causing this crash but it only seem to have started happening after upgrading flutter from 1.17.2 to 1.22.6.
Seem to happen when a user opens a screen with camera preview
I have been using the same version of camera package (camera: ^0.5.6) before and after upgrading flutter.
My methods for initialising and taking pictures have remained the same.
I'm unable to force the crash on my device but I can see quite of lot of crashes occuring on iOS devices since the new verison built with Flutter 1.22.6
Really hope someone can make some sense out of this..
The text was updated successfully, but these errors were encountered: