immediate crash on launch about unitstool HOT 10 CLOSED

@Der-Flip I fixed the apk of the F-Droid store for the v1.0.6, can you confirm it's now working ? As I can close this issue

from unitstool.

Hi, thank you for using the application.

Can you tell me on which store do you installed it (Google or F-Droid), and also the version of the application (I guess 1.0.6?).
Also, do you set some special settings ? Like dark mode, language etc

I'll take a look to it when I'll find time, but thank you for helping me improve the application.

from unitstool.

Hi, my apologies, I knew I forgot something
App Version 1.0.6 via fdroid (droidify)
https://www.f-droid.org/packages/com.unitstool/

Regarding the special settings, I wish I could remember but I don't. I also would've done more testing if the app had started after deleting all app data and reinstalling.

I can do some more checks this evening

from unitstool.

Could you just test to use the version of the Play store to know if the problem can come from the generated apk itself or not ?

from unitstool.

from unitstool.

Ok, so the problem should come more from the apk on F-Droid than from the application itself, it's nice to know.

from unitstool.

You're right, I tested with the last version of the app on the F-Droid store and I have the same problem. But not with the 1.0.5 version, it seems to be the generating process on F-Droid that provide a bad APK for the last version on this store. So by waiting I'm investigate more. You can use the 1.0.6 version of the play store or the 1.0.5 version of the F-Droid store

from unitstool.

The problem seems to be after an update that I made, to solve it, I run this command before generate my apk:
npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle like it said on this issue, so I have to update the yml file on the f-droid side.
The generated apk was asking for Metro server like if I was in debug bug, I don't know really why, but it was the cause

from unitstool.

hi sorry, didn't have time before and didn't realize you pushed it already to f-droid as it still shows 4th August as 1.0.6's publishing date.
Tested it and it does indeed start up now.
Thanks! :)

from unitstool.

Yes, the date hasn't change because the problem was in the apk generation process, not in the source code. So F-Droid display the same date

from unitstool.