This is something that i'm following up as well. I have an app idea in mind but it needs a public database. To be more specific it is for buying and selling stuff so public database is a core functionality. Now i have learned SwiftData as my first persistent database just to find out that it doesn't support public database. Disaster. Now i have to two options, either wait for WWDC24 and see if SwiftData will support public db, either learn Core Data from scratch which will leave me prone to bugs and a lot of struggle as i'm not familiar with CD. Surely i can opt for FireBase as a backend but i don't want that, i don't trust Google simply because they can spy your customers at any time and introduce analytics in your app unannounced. This is something that won't happen with CloudKit and on top of that the project builds faster with CloudKit.

Okay for anyone with the similar problem... I have managed to pay by switching to my 4g network instead of the wi-fi. What a load of bs...

bulangiiilor

alooo salamee

make America great again

imagine in 21 century you are Apple and you can't sort your payment system... dude just take my money ???

heloooooooo ??????????? so useless

Feedback is critical to me since i'll build the MVP. Thank you for sharing those guidelines. I did some research and yes Feedback form falls under data protection regulations In the meanwhile i have implemented a tailored Privacy Policy. It's quite long but here is a highlight when it comes to the Feedback Form it may be useful for the other developers as well

maybe hire another development team such as native iOS developers instead of cross-platforms. Android developers are not up to date with the current rules for the AppStore. There is a high chance they did something wrong in the code

this seems to be fixed once I set up the iOS deployment to 16.4 from 17.