Hi all, There are plenty of posts about app rejection related to this 4.2 guideline (usefulness of your app is limited by the minimal amount of content or features it includes), and mine is not an exception. Every case you can find in the web is different and some cases are indeed very clear (web apps just ported to iOS, simple apps just launching other apps, etc), but some to time you find incredible cases where it seems the reviewer is not really willing to understand your app. I feel I am in this case, and I just hope to find here a good samaritan that can give me a tip to refloat my app :( In the "Next Steps" of the resolution for this type of rejection they say "We encourage you to...offer compelling capabilities or enable people to do something they couldn't do before or in a way they couldn't do it before...". And this is why I said I am on a special rejection case, because my app clearly does something that currently cannot be done anywhere else (not on a web app/service, not in any other mobile app, even on Android). The scope of my app is limited to a community (paragliding and base jumping sport community), so I can understand it is not of course "useful" for everyone, but that is the very same than the usefulness of Candy Crash for my grandmother isn't it? Rejection after rejection I have been improving the UI (so right now the user is basically UI driven), I have added persisting data to the app, etc etc, but they keep saying that my app is useless or not unique, when in fact it is very useful (for its target community) and very unique as nobody else is doing this (basically my app is performing flight model calculations based on Maps and an external elevation model so you can visualise in a theoretically way where and at which altitude you would be flying your paraglide or your wingsuit when launching from a certain point in the map). I tried to explain my case to the reviewer, in case he/she does not understand the real purpose of my app (for example, if you try to use my app in the sea you won't get any data of course because you are at 0m elevation, so no possibility to fly in there) but I am only getting "auto replies" saying my app is still not compliant. I also tried twice to have a phone call with them (as suggested in an email I received from Apple) but they never contacted me... I put a lot of hours on this app (a free app BTW), and I basically feel I am being rejected without any valid reason, and the worst, I don't know how I can counter back all these arguments if they are not listening to me. Sorry for the frustration in my post. I really hope somebody can give me a hint here. Thanks

I have been googling this topic for a while and it seems everybody is experiencing some kind of issues with dismissing modals after the new iOS 14 release, but I have not found anybody also struggling with my specific case. After upgrading to iOS14 (14.0.1 included), all my sheet modals in my app started to act randomly weird: Sometimes the modals act perfectly as usual Sometimes (most of the time) I have to kill the app because the modal is not dismissed and I cannot go back to the main view Sometimes a modal is automatically (non-desired) closed right after it opens, and after that, the modal works fine (and so it is not closed until I say so) Does anybody know what is going on with iOS14 and sheet modals? Should we close modals in a different way than in iOS 13? I tried closing the modals in two different ways: either by using the Binding<Bool> method, or by using the Environment presentationMode method, and while both methods were all working fine in iOS13, now in iOS14 they are all randomly (more than 50% of the time that I open the app) failing.