I am not sure why this is happening, at the first point the service should get crash as in the third value for the showContent function is a text and not boolean, you should have first got class cast exception.
Set the third value of showContent to false or true (for big text)
let me know if this solves, else I will investigate the issue
Hi, this actually looks like a synchronization bug one of the loops is executed late, I will do deep into the issue tomorrow and check what is not working.
I have sent you the project file (nothing is changed), what was happening with you should not have happened at all, it’s totally weird, did you update your extension? how many times?
Because that on your APK was behaving differently from the one of mine.
anyway, I have fixed it and sent you the new project file, removing and reuploading the extension just fixed the problem.
Improved event handling
Components like the PhoneCall component of the AnsweredCall event’s phone number was null sometimes.
The extension couldn’t handle it although the value is not used. This is now fixed
Fixed service start issue on older devices (ref this post)
Hi sorry for the late reply, I needed some time.
Since the android application needs access to phone call permission to be declared in the android XML, that doesn’t work.
Hi, you should try it using the normal blocks as just one feature is not working, every event is watched by the extension. If registered, it forwards it to any event.
Hello @Xoma Remember me the Chat App Person? I have Tried you Methods it Worked out Well but i am not happy with Airtable. So I changed to Firebase RTDB. Is it the same way i should do for Firebase. i am trying from hours but not getting. Please Help ?
The reason is that you will need to pass the arrangement to the background service which you cannot directly just pass it.
There are only a few types of objects like lists, numbers, texts and other things possible to do but not all.
The extension saves the data (arguments, lists, text, numbers, Dict) as a File which is then read by the service to obtain the objects back to their original form directly without any third-party library.
You can see the file in the app directory and a directory named BackgroundTasks/BackgroundTasks<Servicce_ID>.
You cannot directly do not view contents, (it’s encoded using ObjectStream)
Search the topic, it is possible and that’s how the extension works. I don’t know why people want instant solutions.
I agree, extension is complicated to understand, but that doesn’t mean you will be asking such small questions again and again.