WhatsApp is nothing to do with Apple. And you are in the wrong place, again.
If you have suggestions, raise them in the appropriate place. This is NOT the appropriate place.
Your first point is rubbish, anyway. If WhatsApp loses your messages, then that's WhatsApp's fault, and not something Apple can fix.
Second point: Why should Apple make it easy for third-party messaging apps to backup chats easier? It's up to them to do their job, not Apple.
Honestly, I can't go on.
You're in the wrong place, and your post seems like it was written by some mad AI engine.
Post
Replies
Boosts
Views
Activity
These are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding.
These forums are not where Apple's actual developers chat about new features.
If you have a suggestion, you should raise it at: https://www.apple.com/feedback/
Why do you think posting on these Developer Forums is going to help?
These forums are for developers of third-party software for Apple's platforms. WE ARE NOT THE DEVELOPERS OF MINECRAFT. Contact Minecraft, not us.
These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding.
Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.
What code are you after?
You're in a QUEUE. Just wait.
We can't help you because you've given us the bare minimum of information.
This is like saying, "A bit of my car is broken", but not telling us what bit is broken.
What macOS version are you on? How are you installing CocoaPods, etc.?
iOS version? What device is this on?
Maybe you should raise a bug in the usual way...
You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.
These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding.
Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.
It's likely you don't need to send a report because it's an issue in your code.
Show us the block of code that causes the error.
In the meantime, you can narrow it down by commenting out lines of code until the error disappears, then you'll know which bit is causing it, and we can help you.
You should rethink how you do these releases.
You can version an API such that, for example, version 1.0.0 of your app uses version 1 of your API, and any updates to the app also use version 1 up to the point where you need to use version 2 of the API.
When that happens your app update will be sent to App Review and will use version 2 of the API.
Version 1 will still exist and work for the existing users of the currently-released app, and version 2 will be used with the new app.
Thanks for your comment.
Given that these forums are for developers of third-party apps for Apple's OSes - and we aren't actual Apple employees - your comment isn't going to get you anywhere here.
You may wish to take your comment to an Apple fansite instead.
Is there a particular reason you've picked C as your first language to learn? You will likely find Swift a much easier language to learn, and it's built right into Xcode.
If you're set on C, it's not particularly easy for us to determine why you're getting "Build failed" without seeing your code.
Do you have some code for your two examples? Maybe you're doing something wrong, and there's a different way of doing what you want to achieve?
You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums.
You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.