I'm frequently seeing "not responding" dialogs (often referred to as "ANR"s from Arc when switching to other apps from it. This generally indicates that an app is doing something it shouldn't be on the UI thread.
I'm using a Pixel 6a with Android 15 (BP1A.250405.007).
Thank you for the report. We’ll investigate this symptom with development promptly and can see the relevant events in ARC logs from our cloud diagnostic servers.
That’s great, but not really relevant. ANRs are generally a symptom of an app using Android’s UI thread incorrectly and have nothing to do with a networking setup. See the official Android docs for more: ANRs | App quality | Android Developers.
Hi @seadowg,
Just circling back on our request above—would you be open to sharing ADB logs with us? They’ll help our team take a deeper look into what might be going wrong. If you’re able to upload them, just let us know and we’ll take it from there.
Development has requested ADB logging because they are testing resource constraints on this operating system and hardware combination. It’s up to you what you’d prefer to share with us, but we’re only the messenger in this case.
How many apps do you have open synchronously with ARC when this occurs? Does that make any difference?
I’m travelling without a computer right now, so I won’t be able to get ADB logs for you. However, the team should be able to see ANRs reported to the Play Store (see the link to docs I posted earlier). I’m an Android developer and can advise further if that’d be useful - DM me if so.
Do you mean “simultaneously” rather than “synchronously”? I’m on an (Android) phone so can only have one app active (“in the foreground”) at once. I’m not using any split screens or anything to multi task.
Hi @seadowg,
I’ll check with the dev team to see if they think the ANR report includes enough trace detail to help us move forward.
Got it — we were actually asking about background activity. Specifically, were there a lot of other apps running concurrently in the background at the time of the freeze? We’re trying to rule out any memory pressure or background service contention that could be contributing to the issue. Let us know what your environment looked like at the time.
Gotcha! Just looking at my recent apps, it seems like I’d typically have 5-20 apps in there. In terms of background apps (apps that Android highlights as “active” in the notifications pull down), it looks like I’d have 1 or 2 running next to Arc (Pocketcasts and Pebble for example).
Just to clarify, I’m not experiencing a “freeze”: Android is telling me that Arc isn’t responding with the standard ANR dialog like in this example from the Android developer docs (capturing a screenshot doesn’t work for the dialog):
I sadly haven’t found a reliable way to reproduce this issue - it just happens a few times a day. I haven’t seen it happen if Arc is the only app running, but I’m obviously not going to keep my device in that state for very long.
I have tended to see it when switching to another app from Arc (as I said in the initial post) so that might suggest that it is something to do with other apps running, but I’d still be a little surprised: my hunch would be that Arc is doing something it shouldn’t be on Android’s UI thread (potentially on a lifecycle callback fired when switching out of the app). That said, I’ve never seen the code or have any idea about how Arc works under the hood so that’s all pure guess work!
Hi @seadowg,
Thanks for the clarification — that’s helpful. We’ve added this to the ticket with our developers. We should have an update for you soon and will follow up here as soon as we do.
We have ongoing work in this area, but each release of ARC contains incremental stability improvements. As such, we’re curious to hear if you’ve experienced this freezing/crashing or related symptoms since updating to the latest build.
We expect that forthcoming builds will lock this down once and for all as we release further stability work.
Sorry I forgot to include the version in the original post, but I was using 1.65.354 (released April 10th) as far as I know and that’s the latest version.
