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...

 

[Erel]

You need to install it with the Sdk Manager: https://www.b4x.com/android/forum/threads/in-app-update-library.126305/#content

 

[Zeev Goldstein]

You need to install it with the Sdk Manager: https://www.b4x.com/android/forum/threads/in-app-update-library.126305/#content

Thanks Erel

I gave it a brief view and it seems like a drastic process (i will try it in the weekend)
But i don't understand why is it so complex?
Over the years i had many version updates and never had to go through such a procedure?
The app works fine with 12.80 and sdk 34 so "it is only a version update" i think...

Will i have to do it for every update now?

Thanks and have a nice weekend

 

[Erel]

I gave it a brief view and it seems like a drastic process (i will try it in the weekend)
But i don't understand why is it so complex?

I've just tried it myself. It took me 8 seconds to complete.

It is a step that you did in the past. Now you replaced the Android SDK with a new refreshed SDK so the additional component isn't there.

 

[Sagenut]

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...

Did you updated everything?
B4A
New SDK and Resources
New Java 19

 

[Erel]

Did you updated everything?

The InAppUpdate library depends on a component that is not part of the prepacked SDK. It needs to be installed separately.

 

[Sagenut]

I thought that anyway eventually installing only B4A 13 without all the rest could bring to dependencies error or something like.
If his project was working just before updating.

 

[mcqueccu]

As Erel said, if your library depends on some specific components from the SDK manager, you are allowed to update ONLY THAT COMPONENT.

What Erel WARNs is not to UPDATE Everything Recommended by the SDK Manager.

 

[Zeev Goldstein]

I've just tried it myself. It took me 8 seconds to complete.

It is a step that you did in the past. Now you replaced the Android SDK with a new refreshed SDK so the additional component isn't there.

Thanks
One last short question - should i do it with all my apps or once will do it for them all?
If so i can try on one old test app...

 

[mcqueccu]

The component is downloaded to sdk manager for all apps to use.

 

[Zeev Goldstein]

Did you updated everything?
B4A
New SDK and Resources
New Java 19

yes

 

[Zeev Goldstein]

seems something is wrong

this sub is already in my code and it is used to check if there's an update of the app in play store
this did not update the SDK as i was told
i still get

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

so how do i fix this?
i checked another old app - a very small and basic and it did not show this error
so i guess one of the libs or components i use is the cause

should i use sdk manager?
it shows a few recommendations to install but none is the one the error is about

can it be resolved by copy the missing file from somewhere to somewhere?

this app is a critical app for me so i must resolve this

thanks for helping...

 

[MicroDrie]

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

help...

Considering that you have everything (re)installed correctly and that a newer project works without problems you might expect that the problem is project related. What remains is to rebuild the project in steps.

The first question is whether you are able to resolve the error message:

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

(be aware that error messages usually do not provide clarification of the exact cause) to replicate by starting with the minimum requirements to make this function work. If compiling that works without error, you will have to add a piece of functionality from your old program each time, compile it, and continue doing so until the error occurs again.

Based on your observation that a new program works without problems, I also do not rule out that (because you have not updated your program for a long time) Google has changed the way in which you have to offer something. Based on the short cryptic error message, it seems that the compiler may stumble over a modified underlying library(s). Take a critical look at how you will use the function nowadays (is everything still correct, start completely over because sometimes something disappears, or it just becomes a little different).

As always, without an example it is difficult to pinpoint a cause.

 

[Zeev Goldstein]

Considering that you have everything (re)installed correctly and that a newer project works without problems you might expect that the problem is project related. What remains is to rebuild the project in steps.

The first question is whether you are able to resolve the error message:

(be aware that error messages usually do not provide clarification of the exact cause) to replicate by starting with the minimum requirements to make this function work. If compiling that works without error, you will have to add a piece of functionality from your old program each time, compile it, and continue doing so until the error occurs again.

Based on your observation that a new program works without problems, I also do not rule out that (because you have not updated your program for a long time) Google has changed the way in which you have to offer something. Based on the short cryptic error message, it seems that the compiler may stumble over a modified underlying library(s). Take a critical look at how you will use the function nowadays (is everything still correct, start completely over because sometimes something disappears, or it just becomes a little different).

As always, without an example it is difficult to pinpoint a cause.

took your advice and marked all inappupdate so the app doesn't check for updated
still same error
then i removed the library inappupdate and there we are - no more error
the lib's version is 1.10
maybe it is too old?

i can live without inappupdate and let google update the app
but if i can i'd like to restore it

where can i find and updated lib?
or is it something else?

to summarize - now i have no errors so firstly that's good and a big relief - thank you!!

how (if possible) i fix that lib's error - maybe it is only the version?

once again - big thank you!

 

[MicroDrie]

Take a look at AppUpdating 2.0 - update non-market apps and beaware that the post started at a date Oct 19, 2018 and the lasst post Feb 16, 2021 there is no guarantee that the many changes in android have all been incorporated into the library.

 

[Zeev Goldstein]

thanks,
seen that post and i was in view that it meant for non google app store
if it will work with google store than it worth trying
otherwise i think i will let google do the job and update my app as they normally do automatically

 

[MicroDrie]

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.

In April 2022, Google announced that the 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]

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.

In April 2022, Google announced that the 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:



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.

thanks, you saved me a lot of time
in the meanwhile i commented out the section for inappupdate and i will let google take care of it as the normally do - they automatically update the app during night or whenever they want so basically it is not that big issue...
thanks gain for your help

 

[Peter Simpson]

 

[Zeev Goldstein]

View attachment 156507

Thanks
The problem was resolved earlier
It was all because a lib name 'inappupdate' that was responsible for auto update the app.
I removed the lib and relevant code giving up this feature and letting google do their job updating apps from the play store
Problem gone...
Thanks again