Running new app on actual iOS (13.3.1) device crashes on startup: code signature invalid for "path/to/Flutter.framework/Flutter" #49504
Comments
|
|
Currently I'm using a different developer account but I adjusted both to be the same for Flutter config and Xcode but the error is the same.
|
|
Are you seeing the same error on |
|
Thank you! Now it produces a different error. Just weird that running in Xcode produces the same error but now, running with I did try searching for mDNS error with this message This seems like a new error with iOS. Please advise if we should move in #46705 instead then close this issue. :) |
|
@devforey What's the error in Xcode? The signing error still? |
|
@jmagman Yeah, it is still the same. I already |
|
#49693 same behavious with slightly different errors |
I'm having same issue on the same iOS version, but it seems to work on older versions. Is it working on your sims? Have you tried running the app from Flutter master channel? |
|
Having the same issue. |
|
Xcode gives this error: dyld: Library not loaded: @rpath/Flutter.framework/Flutter (lldb) |
|
I have also tried to create a new project on Flutter master channel. |
|
flutter log: flutter doctor -v |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
This still reproduces on iOS 13.4 beta (17E5223h and 17E5233g) |
|
This appears to be fixed in iOS 13.4 beta 3 (17E5241d). @devforey Can you install the beta profile and confirm? |
|
@jmagman I've had the same issue and can confirm 13.4 beta 3 has fixed it for me. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
The bug first appeared in iOS 13.3.1 and is fixed in iOS 13.4 beta 3 (17E5241d). It was not specific to Flutter, was hit at runtime loading an embedded dylib (like Flutter), and can be reproduced without Flutter. It should not impact apps that are already distributed to the App Store (meaning: your customers are not hitting this crash). You should still be able to distribute your application to the App Store. Workarounds:
If you need help implementing these workarounds, please ask your questions on Stack Overflow or another help forum. GitHub issues are for tracking actionable issues for the Flutter team, and there was nothing Flutter could do to work around this bug other than diagnose, report to Apple, and track its progress. If you are seeing a similar crash on iOS 13.4 or greater, please file a new Flutter GitHub issue so we can take a look. I'm going to lock this issue again so this comment stays at the bottom. We will keep it open for visibility, and close after iOS 13.4 has been released. |
|
iOS 13.4 was released March 24. Closing. |
Steps to Reproduce
I'm trying to debug my app into my actual device but it is crashing on startup. Running
flutter runin cmd and running it in XCode provides different error.flutter create appflutter build iosopen ios/Runner.xcworkspaceRunner Project -> Signing & Capabilitiesand select non-developer account team with valid Bundle identifier.with XCode run
Logs
My developer certificate already uses
Use system defaultsin settings.logs
with
flutter runflutter runwith the logs below, I already unchecked
iPhone USB -> Disabled unless neededbut still no avail.Logs
The text was updated successfully, but these errors were encountered: