the native IOS podcast app never notifies me

Following this discussion. I've never reported anything either, for the same reasons - at least not in writing. Nobody seems to take anything seriously unless it is in writing.

The first thing you need to do is to make sure what you're reporting is actually a bug and not a function by design or a problem with your hardware/device.

If you determine that the problem is actually a software bug, then the most important information you need to provide is the exact steps to reproduce the problem. Obviously, you need to include the device you're using, the name of the app (if applicable) and all pertinent version numbers. Also include the values of any settings that might be related to the problem.

In your case, I think the problem might be difficult to reproduce. Check related settings such as Do Not Disturb. Do you get notifications from other apps?

I think in this case, calling Apple Accessibility might be warranted. However, claiming this as a bug might not be the best approach. Just describe your problem and ask them to help you get it to work the way you want. They can help you check the various settings and such that might influence the behavior of your device. If they actually determine that this is a bug, they can report it for you. Likewise, if they determine you have a hardware problem they can tell you what your options are at that point.

Hope this helps.

I’ve called them before. And they are very nice people and I will admit. I have asked if a certain behavior is a bug or not. And they’ve been nice about it. Another thing you could probably do you, is make use of the screen recording feature on your device. This is really good for if you can reproduce certain bags and then you can attach that to an email. Also when you call Ask if they can do a screen share with you. Have your Apple ID ready and give it to them and they will be able to look at your screen. And they will be able to see exactly what you’re seeing. If not a little more. Only in the sense that they can see certain things that we might miss. Like certain buttons changing colors which could indicate certain things.
I have never reported anything by email. Mostly because I like talking to people on the phone. I feel like I get better responses that way and I feel like one on one help is the best thing to have when you’re dealing with tech-support. Whether it’s for a mainstream application or Accessibility related support. Mostly because How voiceover works to take people who have no idea what it does and how it works can be a little crazy to do over an email or chat. I think you’ll get more results if you do it over the phone.

When it comes to bug reports, what you need to do depends on the type of bug you have and how easy it is to reproduce. So just because this one bug may be hard to reproduce, does it mean that another bug won’t be. Of course some steps are still the same. After names, version numbers etc. etc. Also, I would try another server party pad catcher. And see if the same thing happens. All of your podcasts in in 0PML file into a third-party pod cast app. Good ones that I use for overcast, pocket casts, and there’s tons of others. Some free some paid. Both overcast and pocket casts for free. So I would subscribe to your podcast there and see if you still get the same problem. Because that’s one thing they might ask you. And even if they don’t and you tell them, that is goodInformation for them to have.

I will tell you. I had a pretty complex bug that involved me not being able to move apps out of my dock. And yes this was with unlucky 13. And I called Accessibility, they were able to do a screen share, and he was able to see it. Because of the complexity of this bug I had two cats a file uploaded reproducing the bug, and then he had to escalate it up I actually had an engineer assigned to my specific case. And it turned out that this bug was so deep in the coding, that they actually had to rate the septic fixed just for this particular bug. But the advisor that I had on the keys was with me every step of the way. Giving me updates, trying different things, etc. etc. Sorry is it that bug type will probably not happen to you very often if at all. I just happen to be one of the unlucky ones. Yay.
Also another thing, besides being nice about it, ask if what you’re saying is making sense. A lot of times I’ve done that and a lot of confusion has gotten cleared up in that question. It saves everyone time.
I have reported a few bugs. Accessibility wise and with mainstream apps. And for the most part I’ve usually gotten tech-support people, and then you show me there every step of the way. Offer. If you have screenshots, or screen recordings, Even audio recordings. Offer to send them. Or if you don’t have them offer to make them. No obviously if you do that little bit of explanation in there. As well as the obit obligatory information. Type of device version numbers all that happy stuff. I’ve made screen recordings and down screenshots with Weather Gods. And it was actually very thankful when I sent them to him. And when I get those. And then as you’re doing the screen recordings, you can talk them through it. And they will hear voice over in the recordings so don’t worry about that.
Sorry for the long winded comment, but I hope that this helps you in any other people that are nervous about reporting bugs rather it be Accessibility related or not. Or whether you are reporting those bags to Apple or another app. And I also hope that this puts your mind at ease.

Hello there!

My experience with interaction with Apple Accessibility have been nice, even though all my issues were not addressed. On certain occasion, I got typical responses like they're aware of the issue, whereas on other occasion they have actually engaged with it and got resolved. I didn't need to be very typical as to how to report bug, I just explained them the way I could.

Regarding the Podcast notification issue, only thing I'm wondering is whether it would be categorised as accessibility bug. If not, then writing to Apple Accessibility may not help.

Hi. I've heard from other users of the Hindi voice that it's not exactly as good as you would like. I'm basing my theory on the following. Apple was founded in America. It stands to reason, the bugs fixed with any version of any product probably the most of which are English versions of the system and the applications. I'm not saying the podcasts issue is yours alone. I'd probably try to not only write to accessibility, but find even a general contact form. The app store really wouldn't be the place to get something resolved. You mightget a response but more often it seems like a place with reviews and that's just for others to read, not so much companies. I mean no disrespect about the Hindi voice, it was an example of possibly how Apple may not be aware of someone in their own native country having a problem. Also Apple is not blameless being they have in my opinion have to much going on. Ipad Os, IOS, Mac,watch, tv, Apple music. Hardare like the Airpods, Airpower the wireless charging standard. On one end, I'm glad they are expanding. On the other hand I think they can't focus on any one thing but the main features of each version of software. Hope I helped somewhat.

I use it for my podcasts and got a notification today about a podcast being updated.

I'm noticing a bug though and have made a post about it here: https://www.applevis.com/forum/ios-ipados/help-podcast-apps-and-walking

If you Khushi, or anyone else on this thread could follow the instructions in that post and report back what happens, on my thread, I'd really apreciate it.

I think I know what the issue is with Apple podcasts. I’ve experienced this issue myself. There are 2 requirements that must be met, in order for the Apple podcasts app, as well as most third-party apps, to send you notifications about new episodes. The requirements are:
1. You must be on Wi-Fi
2. You must leave the app running in the app switcher at all times

The second requirement is one that most third-party apps have.
The only app that I found that does not have this requirement, is Pocket Casts.

Hi,
I’ve tried many podcast abs, including but not limited to overcast, downcast, icatcher, Castro, and many more. All of these apps require that they be open in the background, in order to send you notifications. They don’t explicitly say that, but I figured that out through trial and error.
For some unknown reason, the Apple podcasts app is also on the list that require this. I don’t understand why podcast apps require this, because it drains your battery very quickly.
I even bought Cosmicast recently, but it too, requires that it be open in the background, to send you notifications.
I have a feeling I’m going to have to call Apple Accessability, and ask them why this is.
If I do end up calling them, and finding out anything, I will post here, so others can stay informed.

If you’re on twitter, that’s honestly the best way to reach him. I’ve tried sending him an email, but he never gets back to me.

I know you're not on twitter. But if you are experiencing this, and you ask others, who are not having a problem, or maybe can't explain it the way you can, how will that get your issue fixed? Simply put, it won't. Maybe create a twitter, ask the question, then only wait for the developer and delete the account? I mean how can someone explain the problem that you're having, if it isn't you?

Hi everyone, developer of Overcast here. The way I’ve implemented notifications usually relies on the app having Background Refresh enabled and remaining in the app switcher (not being force-quit).

I deliver a silent push notification from the servers to tell the app a new episode is available, which should trigger the app to wake up in the background, sync the new episode info, and start the download.

In some cases, iOS won’t let the app wake up, such as if Background Refresh is disabled, if it’s force-quit, if the battery is low, or if the phone is in Low Power Mode. If the app isn’t woken up for whatever reason, it won’t show the notification.

I could do it a more direct way, pushing a text notification instead of a background-update notification, which would display 100% of the time. But if I did that, the app wouldn’t wake up in the background to begin the download, so when you tapped the notification to start the new episode, it probably wouldn’t be downloaded yet.

Hi. Honestly, you are a bit unreasonable. First, having your parent's account post instead of you, even if that's a one and done idea? To me, in my view, distasteful. simply, because you are asking someone else, as I said earlier, to post on your behalf. Second, the developer has since said, I could make a push notification, but that would mean the podcast has not downloaded yet. While I am not familiar with India's wifi conectivity, nor their price exchange, is it not possible to say go to a library and download the podcasts once a week or twice a week? I am asking as I think there's more for your side of the problem to find a solution. I mean absolutely o disrespect or any offense.

I was not at all suggesting it was your wifi connection. That was a question. I also was not suggesting it distasteful that you posted on your Dad's Twitter. I had only meant, you should write to the developer, which you did, so that's over and done. The developer clearly explained that running a push notification instead of the app being in the background, wasn't really an option. Yes, I understand your device is on the older side. Yes, you can't have it always running in the background. But again, he said that your episodes wouldn't be downloaded, after the alert comes up, it would then have to start downloading. when the app is open, all it needs to do is start the download. so this makes perfect sense. In fact, though I don't use podcatchers, this makes sense to me. So maybe when you have a newer device, whenever that is possible, you might be able to leave the app open.