Client side listening Question

I am subscribing and listening for an event, Works perfectly when running the application in debugging, but when I build for release all my features work other than the ones relying on Realtime/Listening. Has anyone ran into this issue before?

Logging in, signing up all of that still works when building for release just realtime/listening stuff breaks

TL;DR

Issue: Realtime/listening feature does not work when building the app for release, but works fine when running in debugging mode. Possible Solution: - Check if there are any additional permissions needed in the AndroidManifest.xml file for realtime to work properly. - Make sure that the app is connecting to the correct Appwrite instance. - Check for any error messages or logs related to the Realtime container. There may be a specific error message causing the issue. - Verify that other Appwrite code is functioning correctly when building for release. - Consider reaching out to others who may have encountered a similar issue.

Weird... Any errors?

none that I'm getting at the moment, I did get one weird one (I got the logs from the realtime container and for the most part runs well), but this will happen sometimes NOTICE ProcessFactory::end() (ERRNO 1005): session#45 is closed after this error things just continue on like normal afterwards (log wise)

and the most confusing part is when running with debugging the feature works flawlessly, when building the apk all my other appwrite code works other than the feature relying on the realtime and event portion of things

Are you connecting to a different Appwrite instance?

in what sense do you mean exactly? Like the actual appwrite backend portion of things? If so i dont believe so, I have my appwrite instance hosted offsite but its the same one i use when running the application in debugging