-
Notifications
You must be signed in to change notification settings - Fork 143
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
fix: iOS app crashing when launched #1826
Comments
Thank you for the report! |
Apologies for the delay. I would very much like to help, unfortunately I cannot find a release with We've been very distracted trying to get ready for iOS 1.0, but we think the bulk of that work is done. If you are seeing a crash, we would very much like to work with you to fix such. We're also available via discord every day: https://discord.gg/shorebird |
The same happens with our app. When I turn the app on and off, it often crashes. app_id: 064891d4-319b-464f-9ab0-b8ed940584f8
|
Thank you. Are you able/willing to share a crash report (typically an ips
file). ***@***.*** also works if you’d rather email than post
here. Thanks!
…On Sun, Mar 31, 2024 at 5:58 PM vidi ***@***.***> wrote:
@eseidel <https://github.com/eseidel>
The same happens with our app.
When I turn the app on and off, it often crashes.
app_id: 064891d4-319b-464f-9ab0-b8ed940584f8
release: 40685
patch: 8
064891d4-319b-464f-9ab0-b8ed940584f8/releases/40685
—
Reply to this email directly, view it on GitHub
<#1826 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADU2TJJXODWL5TAOLWKWRTY3CWLHAVCNFSM6AAAAABFKTB5EGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYHE4DENBYGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
We shared a crash report. Use this !!! |
Thank you! Unfortunately we don't have any iOS releases associated with the account tied to the app_id 4c52f392-ee61-4eae-96ce-7f2c0b61f8a2, so we don't have any binaries to use to "symbolicate" these crash reports with. We would be very interested in helping. However our process is typically to take a .ips file and use the symbols contained in the stored binary to "symbolicate" the crash log so we can see what went wrong. You're also able to symbolicate the crashes yourself using these instructions: We could presumably guess what Flutter version is involved in this crash based on the date of the crash, but using the above described symbolication process will be much more accurate. |
You're also welcome to schedule with me directly and I'm happy to help in person: https://calendly.com/eseidel |
You can see below
|
That's very helpful, thank you! |
I have the same problem
crash log
|
I tested it by distributing it with Testflight and it worked well. We can't test it because we're already in production, but the problem we had before occurred in production. app_id: 064891d4-319b-464f-9ab0-b8ed940584f8 Flutter and shorebird have been upgraded.
|
We believe we know what's going on here and should have a fix out in our next release. We had some code which (wrongly) assumed that the "base" image and the "patch" image were loaded in a specific memory order and would crash on this ASSERT if they were not. That's not a valid assumption and we'll have a fix out shortly which should fix this. @erickzanardo also saw this locally. |
OK, we've fixed this and confirmed the fix locally (of our reproduction). We'll be releasing Shorebird 0.28.1 (Flutter 3.19.5) in a couple hours with the fix. |
The fix was released in 0.28.1. We believe this should be resolved when using Flutter 3.19.5 and Shorebird 0.28.1. Please let us know if you see any other issues! Thank you! |
I had the same issue, was using older(3.16.9) version of flutter and upgraded it today. |
finally. It works. Thanks @eseidel shorebird doctor ✓ Shorebird is up-to-date (1.1s) |
Are you seeing issues in 1.0.0-rc.1 @ilous12 ? |
Ah, sorry, I was reading from my phone and missed some of your message. Glad it's fixed! |
Please don't hesitate to reach out if you encounter any other issues! |
App ID: (insert your app ID here)
app_id: 4c52f392-ee61-4eae-96ce-7f2c0b61f8a2
Description
Steps To Reproduce
Expected Behavior
no error
The text was updated successfully, but these errors were encountered: