I have a problems with two background extensions : Itoo and Taifun LocationService.
On Android 12, Taifun LocationService doesn’t call OnLocationChanged as it is mentionned in the doc. It works perfectly on Android 16.
On Android 16, Itoo CreateProcess makes Android shows a message “Cette application s’arrête systématiquement” (I’m french) and the process never starts, the procedure never starts, etc. But in the other side, on Android 12, Itoo CreateProcess works perfectly.
Do you know these problems and do you know how to fix it ?
Which versions are you using? Always use the latest version.
It would really help if you provided a screenshot your relevant blocks, so we can see what you are trying to do, and where the problem may be.
To get an image of your blocks, right click in the Blocks Editor and select “Download Blocks as Image”. You might want to use an image editor to crop etc. if required. Then post it here in the community.
About versions :
Itoo → Itoo Sky 4.4.2, Date Built 2025-06-20
LocationService → Version 7, Date Built 2025-10-17
I think these are the latest versions.
The Screen1.Initialize bloc starts LocationService and create a process
The left side is what should happen on OnLocationChanged event (send the position)
The right side is what should happen each 10 seconds (check on the server for new notifications to show)
I think there is no mistake in the code, because on my Pixel 3 running on Android 12, the Itoo Process starts perfectly, the permanent notification is visible and the server check works.
But on this phone, the LocationService OnLocationChanged is never called.
And on the second phone, a Pixel 9a with Android 16, the OnLocationChanged works perfectly, but the Itoo Process never starts, and “Cette application s’arrête systématiquement” errors appears when Itoo try to start process (and the server is never checked for new notification). And the permanent notification for Itoo does’nt appear.
So, both features works, each on a different device, with the same apk
Attached you will find an excerpt from logcat for both devices logcat Pixel 3.txt (5.4 KB) logcat.txt (39.6 KB)
, from the moment the application is launched (click) until the following seconds
12-28 12:43:21.406 26134 26134 E isaac_fuentes.: hiddenapi: Accessing hidden field Landroid/widget/TextView;->mCursorDrawableRes:I (runtime_flags=0, domain=platform, api=max-target-p) from Lcom/google/appinventor/components/runtime/TextBoxBase; (domain=app) using reflection: denied
To better understand what happens it might help @Xoma if you could provide the complete log and not only the errors
For the second log file we can see the same error and additionally
12-28 12:33:10.421 23926 23926 E AndroidRuntime: FATAL EXCEPTION: main
12-28 12:33:10.421 23926 23926 E AndroidRuntime: Process: io.kodular.contact_isaac_fuentes.p:doraemon, PID: 23926
12-28 12:33:10.421 23926 23926 E AndroidRuntime: java.lang.RuntimeException: Unable to start service xyz.kumaraswamy.itoo.ItooService@dca3d1a with Intent { xflg=0x4 cmp=io.kodular.contact_isaac_fuentes.p/xyz.kumaraswamy.itoo.ItooService }
12-28 12:33:10.421 23926 23926 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: foregroundServiceType 0x00000008 is not a subset of foregroundServiceType attribute 0x00000001 in service element of manifest file
How did you set the service type for itoo?
Try to use the default service type dataSync instead of mediaPlayback
Please explain also the purpose of your app, you might need a special version of itoo if you have to set another service type
Yes, Taifun, we have talked about this earlier. We have to publish many little extensions with each supports a foreground service tag. Earlier, this functionality could have been achieved using @vknow360’s Manifest Generator Website, which is now offline…
I will see if I can create those little extensions tomorrow…
