WatchOS app crashes/no longer works (SE 1st Gen)
-
Hi,
For several days now, the Apple Watch has stopped working for me. This means that the app on the watch keeps closing by itself. And if I listen to podcasts without an iPhone, playback is reproducibly stopped when I turn/activate the watch so that the watchface is displayed.
My hardware:
- Watch SE 1st Gen (10.6.1)
- iPhone 13 Pro (18.0.1)
Best regards,
Henning -
@quietjoy3883 could you try to:
- Unpair the watch
- Restart both devices (phone and watch)
- Pair the watch again
Thanks a lot!
-
Thanks for the quick reply.
I just invested the time doing that. Unfortunately without any success.
The app still crashes.Also, it seems that the updating/sychronization is not working as it should. On the 1st page of the app, it permanently states that the watch app is updating the data.
I assume that something broke during the last update of the app.
-
Thanks @quietjoy3883 for letting me know.
Unfortunately it’s not related to a particular app update, but we believe it is linked to the watch os update.
We will continue the investigation to find what’s the root cause. I’ll keep you posted.
-
Thanks, that sounds good.
To put it in perspective, though: after I unpaired and re-paired the watch as recommended, I no longer have my filters, downloads, etc., which made the app at least partially usable.
Now nothing is working at all. I don’t even see my podcasts as a result of the re-pairing. So atm the watch app is fully broken for me. -
@quietjoy3883 I can imagine how frustrating this must be. We are working on finding the cause of the problem and hope to have it addressed soon
-
I’m having the exact same problem. Apple Watch S5 (which, like OP’s Watch, can’t be updated to WatchOS 11, so I’m on 10.6.1). Like OP, it didn’t sync properly, but it was partially usable because I already had all my podcasts and UpNext downloaded in there. But after I uninstalled the app and installed it again, it’s basically broken.
Maybe the fact that we aren’t using the latest watchOS versión has something to do with it. I’m willing to bet that a group of iOS devs won’t let their tech get so outdated.
-
@danreylop Thanks for sharing this information with us! Our investigation is ongoing, and you’re onto something. I see all the reports we’ve gotten so far are from 10.6.1.
You can keep an eye on the progress here: https://github.com/Automattic/pocket-casts-ios/issues/2242
-
Hi,
So, the watch app has been completely unusable for about 3 weeks now. I can’t see any progress in the linked ticket regarding all the Apple watches that don’t have or can’t get the latest OS.
What happens now? When will there be a hotfix that will make the watch app usable again?
I personally feel it’s taking too long – after all, we’re talking about a totally broken app here.
-
I see a new IOS update was pushed yesterday – the bug tracked in Github also looks like it was included in that push – but sadly, the refresh and crash issue still exists on my phone/watch (iphone 13, watch SE).
Is the github tracked bugfix for something else? I’m really missing my watch functionality :(
-
The fix has been developed and will be released in the upcoming version 7.76: https://github.com/Automattic/pocket-casts-ios/pull/2338
Therefore, we will recommend trying out again once 7.76 has been released.
-
After reading the Github comments, the problem does not seem to be solved.
It’s frustrating having to change the podcast client after that many years as the app is entirely broken for weeks and there is no clear perspective. -
@quietjoy3883, we’re expecting version 7.76 to be released on or around November 11. That update should include a fix to resolve the issue. If you’re still experiencing it after the update, though, please let us know!
-
@mikerockwell The 7.76 update didn’t fix the issue. I even re-paired the Watch and re-installed the Pocket Casts Watch app.
-
I concur with the above. UI on watch stuck on ‘Refreshing’. The podcast, up next, filter and download list remain blank on watch.
-
Unfortunately, I can confirm: Nothing is getting synchronized for me either and the updated watch app still crashes randomly.
This is incredibly frustrating. And it was foreseeable that this update wouldn’t help (see my previous comment).
You can’t run an app like this… -
Thanks for the update @danreylop, @bluebirdbaby1e81b5d00e and @quietjoy3883
We’re still investigating the issue since you mention the fix has not helped. We hope to have this addressed soon.
If you’d like to join our TestFlight Beta to get quicker access to fixes we are working on, you can email us via
support[at]pocketcasts[dot]comto request access. Note, the beta is likely to have bugs, so if you prefer not having to deal with that, you can stick to the usual stable release via the App Store. -
“We hope to have this addressed soon.”
It’s been a month now, and still nothing works. A bit toooo looong…
Maybe close my subscription? I only pay for the subscription because you put the “Apple Watch- feature” behind the payed wall som years ago.Also, why are we having this discussion on WordPress? A bit unprofessional for a company that take about $5 a month from, I assume, loads of subscribers.
How about building a better website? It has been a nightmare to find support, help and other features online since this problem occurred. -
“We hope to have this addressed soon.”
It’s been a month now, and still nothing works. A bit toooo looong…
Maybe close my subscription? I only pay for the subscription because you put the “Apple Watch- feature” behind the payed wall som years ago.@realslowclapstories We’ve followed up with the developers, and they’ve shared that the issues started with the release of watchOS 10.6.1 and iOS 18. They were not from any changes to our own code, so it hasn’t been easy tracking down the cause(s) of the issue. Since then, they’ve tried to improve sync and background task management to see if the issues get solved, but it hasn’t been easy.
For now, please let us know if you’d like to join our TestFlight beta. This way, you’ll have immediate access to any potential fixes that are released. You can also report to the developers directly on the beta Slack.
Also, why are we having this discussion on WordPress? A bit unprofessional for a company that take about $5 a month from, I assume, loads of subscribers.
How about building a better website? It has been a nightmare to find support, help and other features online since this problem occurred.Paying users have priority access to email support through Profile > Help & Feedback > Get in touch in the mobile apps, if this is what you would prefer.
-