spacemonkey Posted February 23, 2022 Posted February 23, 2022 On 2/23/2022 at 9:02 PM, Jason Carr said: @spacemonkey Thanks, that should be enough. It looks like you're getting the same error as @Eyebrows Cat. I'll see what I can figure out. Expand If you are aware of a location that the message is available as a temp file or some such... let me know and I will see if I can grab a text copy.
Jason Carr Posted February 23, 2022 Author Posted February 23, 2022 @spacemonkey @Eyebrows Cat I'm a bit weirded out, because that com.unbrokensoftware.launchbox.provider reference from the error message isn't anywhere that should matter in the code, but I did remove it from the one spot that it existed, though it shouldn't have been relevant. Beta 6 is out now, and hopefully it might fix the issue? I've been testing on Android 9 with an Amazon Fire tablet, but it doesn't seem to have these issues. @Eyebrows Cat What device are you using and what version of Android is it running? 1
bundangdon Posted February 24, 2022 Posted February 24, 2022 (edited) On 2/23/2022 at 5:48 PM, Jason Carr said: Thanks, that might be helpful. Is that similar to the issue you're getting @bundangdon? I also need to know what devices are having this issue. Expand Yep, that looks like the same error. I'm using a Galaxy S10e with Android 9 installed. And I tried the latest beta that was just released (now) and it seems to be working fine again. Thanks a lot! Edited February 24, 2022 by bundangdon 1
spacemonkey Posted February 24, 2022 Posted February 24, 2022 On 2/23/2022 at 9:21 PM, Jason Carr said: @spacemonkey @Eyebrows Cat I'm a bit weirded out, because that com.unbrokensoftware.launchbox.provider reference from the error message isn't anywhere that should matter in the code, but I did remove it from the one spot that it existed, though it shouldn't have been relevant. Beta 6 is out now, and hopefully it might fix the issue? I've been testing on Android 9 with an Amazon Fire tablet, but it doesn't seem to have these issues. @Eyebrows Cat What device are you using and what version of Android is it running? Expand I managed to get 1.1 beta 6 installed but it appears the issue is somewhat to do with the auto installer. I deleted the contents of /launchbox/updates Launched 1.0 > it prompted to update > downloaded > prompted to install > failed with error message I closed Launchbox > file browsed to /launchbox/updates/ selected 1.1 beta 6 > it installed ok. Regards, Mat
Vader Posted February 24, 2022 Posted February 24, 2022 @Jason Carr Thanks for keeping up with all the issues that have come up as you navigate around the crappy rules setup by Google. You are doing an awesome job. A couple of things I would love to see next include: search/skip by letter add game descriptions refine search (currently the search option is very broad) customizable themes Hopefully you have these items in mind. Launchbox for Android is becoming something special. God Bless and have a good day. 2
Soop Posted February 24, 2022 Posted February 24, 2022 (edited) I'm getting this error now since the last two updates: Edit- ignore, I reimported and it's working again now. Edited February 24, 2022 by Soop
sage2050 Posted February 24, 2022 Posted February 24, 2022 import is creating two copies of games with m3u playlists, even when the m3u is name the same as the game ( ie GAME (USA) (Disc 1).cue and GAME (USA).m3u ) I hear launchbox can create m3us, but i already had them.
Eyebrows Cat Posted February 24, 2022 Posted February 24, 2022 On 2/23/2022 at 9:21 PM, Jason Carr said: @spacemonkey @Eyebrows Cat I'm a bit weirded out, because that com.unbrokensoftware.launchbox.provider reference from the error message isn't anywhere that should matter in the code, but I did remove it from the one spot that it existed, though it shouldn't have been relevant. Beta 6 is out now, and hopefully it might fix the issue? I've been testing on Android 9 with an Amazon Fire tablet, but it doesn't seem to have these issues. @Eyebrows Cat What device are you using and what version of Android is it running? Expand This environment is Xiaomi MI Pad 4 / Pixel experience plus (Based on android 9 / rooted). I'm still getting the same error.
Eyebrows Cat Posted February 24, 2022 Posted February 24, 2022 On 2/24/2022 at 8:44 AM, spacemonkey said: I managed to get 1.1 beta 6 installed but it appears the issue is somewhat to do with the auto installer. I deleted the contents of /launchbox/updates Launched 1.0 > it prompted to update > downloaded > prompted to install > failed with error message I closed Launchbox > file browsed to /launchbox/updates/ selected 1.1 beta 6 > it installed ok. Regards, Mat Expand I was able to update this way. thank you.
Jason Carr Posted February 24, 2022 Author Posted February 24, 2022 On 2/24/2022 at 8:44 AM, spacemonkey said: I managed to get 1.1 beta 6 installed but it appears the issue is somewhat to do with the auto installer. I deleted the contents of /launchbox/updates Launched 1.0 > it prompted to update > downloaded > prompted to install > failed with error message I closed Launchbox > file browsed to /launchbox/updates/ selected 1.1 beta 6 > it installed ok. Regards, Mat Expand On 2/24/2022 at 6:02 PM, Eyebrows Cat said: This environment is Xiaomi MI Pad 4 / Pixel experience plus (Based on android 9 / rooted). I'm still getting the same error. Expand Thanks guys, so it looks like we've fixed the APK so that it actually installs, but we must still have an issue with the code that installs the APK, from what it sounds like. I'll see what I can do to get that fixed for the next version. Unfortunately though, even if I do get it fixed, you'll need to manually update to the next version (at least), since the updater will be using the current code to update.
Jason Carr Posted February 24, 2022 Author Posted February 24, 2022 On 2/24/2022 at 1:43 PM, Vader said: @Jason Carr Thanks for keeping up with all the issues that have come up as you navigate around the crappy rules setup by Google. You are doing an awesome job. A couple of things I would love to see next include: search/skip by letter add game descriptions refine search (currently the search option is very broad) customizable themes Hopefully you have these items in mind. Launchbox for Android is becoming something special. God Bless and have a good day. Expand Thanks, yup, all of those we do have in mind. On 2/24/2022 at 2:06 PM, Soop said: I'm getting this error now since the last two updates: Edit- ignore, I reimported and it's working again now. Expand Yeah, I have seen that before. I think this happens when the app is killed during the XML generation, which we already work hard to prevent, but apparently it's not quite 100%. I'll be revisiting this for the next beta. On 2/24/2022 at 5:55 PM, sage2050 said: import is creating two copies of games with m3u playlists, even when the m3u is name the same as the game ( ie GAME (USA) (Disc 1).cue and GAME (USA).m3u ) I hear launchbox can create m3us, but i already had them. Expand Good to know. In general, we need a better way to filter game file types on imports, so we'll probably tackle this when we tackle that.
spacemonkey Posted February 24, 2022 Posted February 24, 2022 On 2/24/2022 at 7:10 PM, Jason Carr said: Thanks guys, so it looks like we've fixed the APK so that it actually installs, but we must still have an issue with the code that installs the APK, from what it sounds like. I'll see what I can do to get that fixed for the next version. Unfortunately though, even if I do get it fixed, you'll need to manually update to the next version (at least), since the updater will be using the current code to update. Expand Good work Jason. Looking forward to whatever comes next. It's a great front end on both PC and Android. 1
Jason Carr Posted February 24, 2022 Author Posted February 24, 2022 @spacemonkey @Eyebrows Cat Sorry, one more question: do you know when the updater stopped working for you? Did it work with previous versions?
spacemonkey Posted February 24, 2022 Posted February 24, 2022 On 2/24/2022 at 7:24 PM, Jason Carr said: @spacemonkey @Eyebrows Cat Sorry, one more question: do you know when the updater stopped working for you? Did it work with previous versions? Expand I have the APK installed on my Fire Cube (Fire TV), and Retroid Pocket 2+. Updater stopped working on both with 1.0. I've just manually installed 1.1 beta 6 on the Fire Cube successfully. 1
Jason Carr Posted February 24, 2022 Author Posted February 24, 2022 LaunchBox for Android 1.1-beta-7 is out now with the following: More robust data saving and loading (including backup files) Hopeful fix for the above updater issues for some devices on Android 9 and below Keep in mind that even if the updater is fixed for those devices, we'll unfortunately only know when we update the *next* time, not this time. For this update, folks were having issues with the automatic updater will unfortunately have to still manually update.
Eyebrows Cat Posted February 24, 2022 Posted February 24, 2022 On 2/24/2022 at 7:24 PM, Jason Carr said: @spacemonkey @Eyebrows Cat Sorry, one more question: do you know when the updater stopped working for you? Did it work with previous versions? Expand In my environment it occurred when installing 1.0-beta-5 and the error has continued since then.
Eyebrows Cat Posted February 24, 2022 Posted February 24, 2022 On 2/24/2022 at 9:01 PM, Jason Carr said: LaunchBox for Android 1.1-beta-7 is out now with the following: More robust data saving and loading (including backup files) Hopeful fix for the above updater issues for some devices on Android 9 and below Keep in mind that even if the updater is fixed for those devices, we'll unfortunately only know when we update the *next* time, not this time. For this update, folks were having issues with the automatic updater will unfortunately have to still manually update. Expand LaunchBox for Android 1.1-beta-7 was successfully installed by the automatic installer. Thank you Jason!
Jason Carr Posted February 25, 2022 Author Posted February 25, 2022 On 2/24/2022 at 11:20 PM, Eyebrows Cat said: LaunchBox for Android 1.1-beta-7 was successfully installed by the automatic installer. Thank you Jason! Expand Ah, so that means it was actually fixed in the previous version, lol, of course. That makes sense. Good to hear. 1
spacemonkey Posted February 25, 2022 Posted February 25, 2022 On 2/25/2022 at 12:09 AM, Jason Carr said: Ah, so that means it was actually fixed in the previous version, lol, of course. That makes sense. Good to hear. Expand I concur. 1.1 beta 6 auto updater updated to 1.1 beta 7 without incident on my Retroid Pocket 2+. Fire Cube next 👍 2
ZeroZorro Posted February 26, 2022 Posted February 26, 2022 Starting empty adding ROM's was no problem, but selecting to play gives this error. Beta 6 on Nvidia Shield with updated firmware (9.*) Any clues?
Recommended Posts