I am still learning how to code and the main reason for posting this question is to learn and improve. Thank you for reading my question and perhaps giving an answer. But I think my approach to this issue is not the best and there should be a better solution to this. My question is, is the above a good approach and if not, what would a better solution be? If there is no better solution, can I store this session key for only 5 minutes for example? I know I could flash a session key, but when re-submitting the form, it would again check for aliases because the session key does not exist. Then, when I come back to adding a new track, the warning is being shown since the session key aliases is still there. So the issue is, when I submit the form, the session key aliases is set, and then I go to another page or close the website. ![]() Then, if I do NOT re-submit the form, this key is of course saved, and the warning will be shown every time when I am trying to add a new track, until I hit submit. ![]() When submitting the form for the FIRST time, AND an alias has been found, the session key aliases is set. All of the above works exactly how I want it to work. Here I check for the aliases and put them in my session Thanks in case anyone knows how, thanks in advance. I did a good search, but I didn't find anything that could help me solve this problem. Has anyone see this before or is there a bug exclusively on Pixel devices that run Android 12? I've spent hours digging into this and am at a complete loss. The only thing that's changed with any of those recently is we updated WorkManager to initialize itself using Android's app startup library, but I'm not sure if that's even relevant since the crash logs give me no information, and if there was a problem with our implementation it wouldn't limit itself to just Pixel devices running Android 12. We have a custom FirebaseMessagingService to listen for notifications that we register in the Manifest and a couple of BroadcastReceivers that listen for geofencing updates and utilize WorkManager to do some work when a transition is detected. I've looked at similar questions (like this and this) but Crashlytics is showing that these users all have plenty of free memory, and nowhere in our codebase are we calling registerReceiver or sendBroadcast so the solutions in that second question aren't any help.īased on limited logs I'm pretty sure the crash happens when the user receives a push notification, but I have a Google Pixel 4a running Android 12 and I haven't been able to reproduce it at all when sending myself notifications. Melco is aware of this problem with the internal partition becoming full and is working on a solution. I suggest that you install MinimServer first, check that it is working, and then install SongKong. ![]() Fatal Exception: $CannotDeliverBroadcastException: can't deliver broadcastĪt (ActivityThread.java:1939)Īt $2700(ActivityThread.java:256)Īt $H.handleMessage(ActivityThread.java:2190)Īt android.os.Handler.dispatchMessage(Handler.java:106)Īt android.os.Looper.loopOnce(Looper.java:201)Īt android.os.Looper.loop(Looper.java:288)Īt (ActivityThread.java:7870)Īt .invoke(Method.java)Īt .RuntimeInit$n(RuntimeInit.java:548)Īt .ZygoteInit.main(ZygoteInit.java:1003) After doing this, you should reinstall MinimServer and SongKong.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |