![]() This log occurs when there’s a broadcast intent, a hint for applications that audio is about to become ‘noisy’ due to a change in audio outputs, such as when Bluetooth disconnects from the device. ![]() If you’re using ad blockers, firewalls, VPNs, or anything else that could be blocking our app, you might encounter this issue. This error usually occurs when something on your phone is preventing our app from accessing an internet connection. Refresh failed: with error The Internet connection appears to be offline., status code 0 This log indicates the playback speed was changed from a Bluetooth device like a headset. Remote control: changePlaybackRateCommand This log means playback was resumed from a remote device. Remote control: pla圜ommand, treating as playPause This log indicates that an incorrect email address was used to log in.Īs the name suggests, this log indicates that the sync was successful. Unable to obtain token, status code: 401, server error: login_email_not_found The app also refreshes automatically occasionally. This command pops up when the app is manually refreshed or opened. This log means the podcast episode is encoded in a format their phone can’t play. This error may also occur when using Chromecast, but that’s due to a bug in Chromecast, not in our app.ĮxoPlaybackException: Source error UnrecognizedInputFormatException The solution is to ensure it is set to ‘Unrestricted’. We’ve found that this often occurs on Android 12+ devices which have the Pocket Casts app using ‘optimized’ or ‘restricted’ battery settings. This log indicates that playback was paused from a remote device like Bluetooth headphones.įoregroundServiceStartNotAllowedException Essentially, the issue causes the player to run out of memory. This error may indicate that the user’s problem is related to an ongoing issue we have where videos that are encoded in certain ways can crash Google’s own ExoPlayer framework, which we use for the Android app. : Failed to allocate a 32 byte allocation with 186600 free bytes and 182KB until OOM, target footprint 536870912, growth limit 536870912 failed due to fragmentation (largest possible contiguous allocation 2621440 bytes) Unfortunately, this error is not recoverable and requires you to uninstall and reinstall the app. This log means the database is corrupted. If false, then all play time of the app is over, and Android will stop all playback permanently.Ĭaused by: : database disk image is malformed (code 11 SQLITE_CORRUPT) If this is true, Android will pause play for a bit, then let it keep playing. This indicates whether the loss of audio focus is temporary (like when a notification plays) or permanent (like when you hit play in a music app). The term “focus lost” is Android’s way of saying this. It’s Android’s way of telling our app to stop playing because it’s about to play something else. If your podcast is pausing unexpectedly, this log could be the culprit. AUDIOFOCUS_LOSS: true AUDIOFOCUS_LOSS_TRANSIENT: false This suggests the app’s calls to our refresh server are either timing out or causing server errors. ![]() Refresh failed: response returned no data, status code 504 Here’s a list of the most common logs that you might see: This file contains a list of logs that help us understand what’s happening with the app. These logs can be accessed via Pocket Casts > Profile > Settings > Help and Feedback > then click the ‘logs’ icon on the top right. When you encounter issues with the Pocket Casts app, you may be asked to check your debug logs to help troubleshoot the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |