Hello,
I've been encountering a persistent issue with my OutSystems application, and I'm hoping someone here can provide some insight or guidance on how to resolve it.
The problem occurs whenever I try to install or uninstall other applications on my device. Regardless of the application being installed or uninstalled, I consistently encounter the same error message, which you can see in the attached screenshot.
I've tried troubleshooting this issue extensively, but I haven't been able to pinpoint the root cause. I'm unsure if the problem lies within my application or if it's related to some external factor.
Could this be a compatibility issue with the OutSystems platform or a conflict with other applications on my device?
I've reviewed my application's code thoroughly, but I haven't been able to identify any specific triggers or errors that might be causing this behavior.
If anyone has encountered a similar issue or has any suggestions on how to diagnose and fix this problem, I would greatly appreciate your insights.
Thank you in advance for your assistance.
Error:
Whenever I go on this link is something like this This error has been pretty much a cancer
Hi Carlos,
Maybe a stupid question, but what version of OneSignal are you using? It seems that several files could not be found for some reason.
How are you building the application? Based on your screenshot it only seems to build for Android. Is the build type debug, release or Google Play? Maybe changing the MABS version will help in generating the mobile application.
Since this is a supported component, you could also ask OutSystems to help find the root cause of this issue.
Sorry, but based on this I do not see the root cause problem.
Best,
Bart
Hi Bart,
First of all thank you for answering, I am currently using the latest version 3.2.3 of the OneSignal.
Is a complex app, I am trying to release the app on Android and on MABS 9.0
Already tried contact Outsystems but not successful on fixing this error.
Hmm, I am afraid I am not of much more help here. Did you try OneSignal in a dummy app to see if it works there? Maybe something in your application is conflicting with OneSignal at the moment.