My 1 bugfix update got rejected because I link to my website.
How are my fellow Mac app developers dealing with Apple's last gasp crackdown at their anti-steering provisions?
Are you making entirely separate versions of your website? Are you using query args to change behavior?
Following up: I resubmitted with ?build=MAS on the offending links. Those pages strip the query string and change my Buy Now button to reopen my app to its Unlock screen.
Apple approved the update.
Whether they approved because of the changes, or just because, we'll never know.
@jmfd on the Bezel Helper page that we link to we stripped the main menu to be compliant.
We simply don’t link to the general website for the reasons you describe here. I don’t like to have a redacted version of the site, I’m afraid that will confuse users. If they’re looking to buy directly it will make them think that option doesn’t exist. I wouldn’t notice myself that some query param is hiding options for me.
Website: https://getbezel.app
Helper page: https://getbezel.app/helper
@mathijskadijk thanks! I may need to do it this way yet.
In particular I have links to the app's main product page and a learn about the pro/compare page that they don't seem to like.
I just submitted a solution where I add query args to the URL and if those exist my 'buy now' button will use an app url scheme to open the in-app's payment page. We'll see what they say (I don't persist this across reloads and there's plenty of other ways to get to our store).
Jonathan Deutsch
Mathijs Kadijk