-
Notifications
You must be signed in to change notification settings - Fork 52
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
App crashing #382
Comments
Hey, |
I was about to raise a separate ticket about Webrtc, but it sounds like you're aware of a potential issue already. When I use mjpeg camera it is pretty stable but since switching to webrtc camera it crashes frequently, almost every time I open it, it'll crash after a few seconds. Quite often it won't connect to the printer or won't load the camera, if I force stop the app it'll work for a short while then the app just instantly closes, it'll keep closing after a few seconds every time I open it. Happy to provide some logs etc if it helps. |
I am still looking into it. For me and many other IOS users it is working fine.
|
I've got the log files but will need to sanitise them when I get back to my computer as they contain PII. Here's a quick excerpt of the errors I see:
App: 2.7.1-511 I'll update later with full logs. |
Thanks, Ill dig into that. But it seems like the Flutter Logs arent helpful at all. Edit: Can you also provide me the version of crownsnest? |
Crowsnest version I'm using is: v4.1.9-1-gd75a3aeb |
For anyone experiencing this issue, can you please confirm whether your webcam supports H264 by checking the crownnest.log file?
|
I just finally found this thread, been having the issue myself for a while. I am using a raspberry pi cam 3, i don't even show supported formats in my logs. I did using a previous logitech usb camera. This is everything i show from startup.
|
After the latest update, the app (on Android 12) now just crashes/shutsdown after a random amount of time.
Before the app actually closes, it becomes very choppy and unresponsive.
Logs are attached
mobileraker_2024-07-08T19-19-44.log
mobileraker_2024-07-08T19-22-47.log
mobileraker_2024-07-08T19-27-41.log
mobileraker_2024-07-08T19-28-03.log
mobileraker_2024-07-08T19-19-24.log
The text was updated successfully, but these errors were encountered: