Raghwendra Singh

Any update on this? We ([Audiomack](https://audiomack.com/)) are also experiencing the same problem. Could someone please have a look. ``` 34134 bytes retained by leaking objects Signature: 0f0ab14a66b16eeae7988b3415bfdc35ce9d42 ┬─── │ GC...

This is a follow-up ticket to the one that was previously closed #553. The problem is still present. I'm including the most recent stack trace for reference. We are using...

Obviously @aboedo, I understand how annoying and frustrating it will be for you; we feel the same way. We sincerely appreciate your ongoing assistance with this issue. Sure, let's wait...

Hello @taquitos @aboedo, Just a friendly follow-up. I can now see few new releases. Does this contain the migration-related changes that we discussed in the comment above? Recently, we had...

> @raghav2945 We are still working on that BillingClient 5.0 migration and we haven't publicly released any of the changes. We also have not made any other fix regarding this...

We began receiving a distinct **ANR** (**_com.onesignal.FocusDelaySyncJobService_**), which appears to be comparable to the one but lacks sufficient details due to the lack of a stacktrace. However, the number of...

Hello @jkasten2 I'm not sure why you put the crash task in here. As I'm receiving the ANR in the OS util component, I'm assuming you've attached the task here....

@JurajKuliska Disabling location isn't helping us at all. We disabled it only at the start, but it appears to have no effect.

> @raghav2945 `FocusDelaySyncJobService` was removed in PR #1515 and was released in [4.6.6](https://github.com/OneSignal/OneSignal-Android-SDK/releases/tag/4.6.6). > > While `OSBackgroundSync` still exists and is being used for location and un-synced player properties it...

Surprisingly, it reappeared with the upgrade from 5.6.4 to 5.6.5. Could someone please take a look? We had seen very few incidents prior to this upgrade; now, the count is...