help 01-14 12:12:57.582 E/ActivityThread( 7457): Service xyz.kumaraswamy.itoo.ItooService has leaked IntentReceiver xyz.kumaraswamy.itoo.ItooService$EndActionReceiver@ef3ab11 that was originally registered here. Are you missing a call to unregisterReceiver()?
What did you try? Show your blocks regarding this extension. Have you registered the events property? Called it properly?
LM_Express (3).aia (3.7 MB)
I think, by reading the error, may be, This error comes from the Itoo extension itself, not from your blocks.
Inside ItooService, it registers a broadcast receiver (EndActionReceiver) to listen for a stop command, but it only unregisters that receiver when the stop broadcast is received. If the Service is destroyed by Android without that broadcast (for example, when you kill the app), the receiver never gets unregistered → “IntentReceiverLeaked” warning.
As a user, you can’t call unregisterReceiver() because it’s inside the extension. What you can do is:
Always call Itoo’s StopProcess / Cancel block when you’re done with the background task.
Avoid leaving the service running when you don’t need it.
This warning is often harmless and doesn’t mean your logic is wrong, but it’s good to be aware that it’s a small cleanup issue in the extension rather than in your own project.
If you want, you can paste a short log excerpt (a few lines before and after that error) and your Itoo block setup, and I can help you check whether there’s anything in your logic that might be triggering the leak more often.
May be the extension author will clarify you better than me. Have you used any block to stop process? When do you receive such error? Pls give us few more details, actually this itoo was an great extension from the mber @Xoma
Can you expkain why you are using method RegisterBroadcast? I do not see you using method Broadcast nor method UnregisterBroadcast.
From the documentation Open Source • Background Tasks: Itoo 🚀 - Extensions - MIT App Inventor Community
You could store property motorista directly in the main procedure run…
Taofun
Hey @Still-learning, this error is mostly fixed on all the latest versions of the Itoo extension. I haven’t seen this case of error reported elsewhere. Perhaps it might help if the blocks used were shown…
Also I’m mostly not programming nowadays… atleast until March when my 12th exams are finished…
2 Likes
I second the suggestions by Taifun after seeing the blocks… It’s very unnecessary to use the RegisterBlock just to store a property in Itoo’s preferences… Just store it directly.
What 12th exam!!! Amazing!!!
1 Like
how to change the foregroundServiceType?
I tried to change it according to the blocks but got this error:
If they ask “why does it need to be changed,” you can say that:
Starting with Android 14 and reinforced in Android 15, Google introduced strict limits on the dataSync type of service (data synchronization).
24-hour window: The system provides a total “time limit” (usually around 6 accumulated hours within a 24-hour period) for services of this type to run in the foreground.
Exhaustion: When this time runs out, Android prevents the service from starting again and throws this exception, causing the app to close (crash).
I noticed your’e storing your values using tinyDB which already another issue itself, you should use the Itoo store property blocks and fetch is also using Itoo
Thank you for the report. This was unexpected. May I ask you for what you are using Itoo for in the background service? If there is a specific need, I can change the foregroundServiceType for you.
It seems that the ForegroundServiceType does not work on its own and requires XML changes for each type of service. For mediaPlayback see here:
I need help adjusting itoo to work like this. The Ideal Type: remoteMessaging
In Android 14+, Google introduced the remoteMessaging type. It was created specifically for services that need to maintain an open connection to receive critical messages from a server.
You have to wait for a specially modified itoo version for this
Meanwhile what about fixing your other issues while using the default foreground service type?
Taifun
2 Likes
I will go through this issue this weekend.
1 Like
I’m also having the same problem with my apps, and I’m also waiting for a solution. Thank you very much.
Read the already given answers in this thread to fix the issue “Service xyz.kumaraswamy.itoo.ItooService has leaked IntentReceiver”
Also what about providing a screenshot of your relevant blocks and explain what you are trying to do?
Taifun
I need a solution to the problem, please. I have a small package pickup and delivery app. I use iToo for the delivery drivers to receive delivery notifications. Due to an error, the drivers’ app is crashing, and they are having to reinstall it to get it working again “frequently.” Please help me. Also, if you could get iToo to receive notifications directly from a server, that would be perfect for my use.
Hello @RV_Delivery, I’m currently between my exams. I’ve already started working on it, but perhaps you can sponsor a quick update in your interest?
Hi, I can help with sponsorship, yes. I would be extremely grateful if you could make these updates. My contact email is: rivinhahugo@gmail.com
Vitor Mori