Android Question b4a 13.0 problem in compile after update - urgent...

[Zeev Goldstein]

hi

i have an old project that was running perfectly under b4a 12.8 (the previous version) and sdk 34
i've just updated to b4a ver 13.0 and got this error while compiling

Maven artifact not found: com.google.android.play/core
Source: InAppUpdate

tried a new sample project and it running perfectly so it must be something with the project (i think)

help...

 

[mcqueccu]

I have problem with the inAppupdate library since B4A 12.80, where it even though it triggers update, it got stuck in the update loop. So I stopped using it.

I really like the library, but had to let it go as well.

 

[MicroDrie]

As I wrote in an other post, in April 2022, Google announced that the InAppUpdate core library has been split into 4 separate modules. The release notes for the split Play In-App Updates Library from 2.1.0 (May 2023) state:

Added support for the upcoming Android 14 release. Apps targeting Android 14 and later should upgrade to this version.

Given the date, I don't expect the AppUpdating 2.0 version to still work. The AppUpdating 2.0 library developer indicated in May 2024 that he would like to update it, but that he has little time for it. You can subscribe via the watch function of the post.

 

[Zeev Goldstein]

ok,
got a replacement idea
keep a text file on your server or anywhere with the latest version number
in the app download the file and compare the version to the one in app
if the one in the file is later - it means there's an update and just refer the user to the store or open it on the app
every time you update and get the message it is alive - update the file
simple but most efficient - and no need for that lib...

 

[MicroDrie]

I used the same method in the nineties at my work. Some caveats: The question is when do you test if the latest version is in use? If the user lets the program run endlessly (in the background), a test only at startup makes little sense. Depending on how dynamic the updating has to be, you can choose to perform the check when the function is updated or you use a timer function.

 

[Zeev Goldstein]

I used the same method in the nineties at my work. Some caveats: The question is when do you test if the latest version is in use? If the user lets the program run endlessly (in the background), a test only at startup makes little sense. Depending on how dynamic the updating has to be, you can choose to perform the check when the function is updated or you use a timer function.

it is all depending on the app's nature
most apps don't need such mechanism as google will automatically update them
in some cases where it is critical to use the most updated version a check at starting the app is good
if the app is running in memory all the time maybe a timer will do
for my app this method is fine and i'm not even sure to use it as i trust google to do it for me