Hi
I'm trying to find a simple working example of a background task to understand how it's working but I can't find any. I read all the threads about that subject but they are all at least 1 y old and most of the blocks are deprecated.
Is there an updated version of the extension ? I feel that if things change so fast then even if I get something to work it might not a few months after.
I'm trying to make mqtt receiver work in the background and set an alarm if need. The alarm extension works fine when the app is in the foreground but need to be able to set it when the app runs in the background.
Hi! I have the same issue with the following error message: No such service ComponentInfo{edu.mit.appinventor.aicompanion3/xyz.kumaraswamy.itoo.ItooJobService}
I tried using both the emulator and building the app and testing on my phone (in which case there is no message but nothing happens). My blocks are attached.
Essentially this just waits and checks if all data is received from tinywebdb before proceeding. I never received the message from the notifier implying the block is never executed, am I missing something or applying this incorrectly? For reference I had messages with similar notifiers in other blocks as well and the messages were displayed without any issue. Thanks!
I can't connect to mqtt. I could use some help. I share only the important blocks sorry for the small appearance I couldn't find how to share only a part of my blocks.
What I want to do is start my app normally with all the interface blocks and catch the event when the app is closed or sent to the background or the mobile does to doze mode, then start the background process (blocks with the Itoo extension)
Is that the correct approach ? Or do I have to connect via Itoo extension blocks from the beginning even if the app is in the foreground ?
I would appreciate the help, I already updated my project to this latest version, but my problem persists and it is the following, the process works very well for me in the foreground or in the background but when I lock my phone it no longer works, this happens on some phones and in others not, there is a way to prevent the service from stopping working with the mobile phone locked?
I updated the variables like you said but still can't connect to mqtt.
So my question remains. The blocks that are used for the interface can cause the code to malfunction? I need them when I start the app. After I close the app or send it to the background I need the mqtt still receiving in the background
It is unfortunately completely dependent on the model and the manufacturer.
This problem does not exist on Stock Android, rather custom skins of Android manufacturers use.
For improvement, you can disable any battery optimization (Android 10>)
There isnt really much you can do about it.
Google had promised to enforce Android standards, such that the behavior across all the devices are uniformed, but this promise has not been fulfilled.
It may also help if you post your relavent blocks of the project.
As said before, you cannot use UI components in background AT ALL. In background process there is NO UI, therefore you cannot perform such actions.
In the meantime, for testing, you can use Notifications extension to debug and report information:
If you are really interested in reporting the changes directly to the user via user interface, then you would need to use broadcasting communication methods added in the latest version of the extension.
Please take a look at the following.
The "clock2.Timer" event runs smoothly. I get the random numbers on the notifications but the "UrsPahoMqttClient1.MessageReceived" doesn't run in the background like it should. It's working fine when the app is open but not when it is closed.
Could this be a limitation of the UrsPahoMqttClient extension ?
Yes exactly, you need to completely move the connect functionality to the background. Only maintain one connection for the background and that would be enough.
