parrots

No worries, if I was a bad actor you'd be doing the right thing, and as many have already pointed out more often than not it is a bad actor. It's tough (trying to be) of the good guys not abusing the system chasing revenue at all costs, no worries.

I don't use local push notifications for advertising, either. I use them for A) location-based recording reminders created by users and B) notifications when a recording from the Watch is synced to your phone and ready to view, since that can take a minute or so if you're off wifi.

I remember one person reaching out shortly after the iOS 13 launch that I trigged the "Slopes has been using your location in the background" notification when I wasn't recording, which was an error on my side and I fixed that right away.

I did have an email or two go out around Christmas for a giveaway, so I certainly had some email marketing in play then. Maybe Slopes appeared in a notification from your mail client? But Slopes itself did not trigger any notification, push or local, for that campaign.

I'm really hoping Apple keeps a log of pushes, because they'll happily be able to tell you that the only pushes I send with Slopes are silent content-available notification for sync engine stuff. I have never sent any user-visible notification, and you're likely mistaking an in-app call-to-action as a push notification.

Apps that use push for marketing deserve hellfire, even if they are little indie shops. Being indie is no excuse for abusing things like push. We have to be scrappy, but we can do so without being spammy.

People are still complaining about section 8 - the remote kill switch? I remember only one instance of an app remotely killed, and that was malware.

Even apps that enabled tethering, emulating, or are otherwise against the rules but make it through review have been simply pulled for sale, never terminated using this capability. I think Apple has proved they're using this responsibly after 6 years.

"Not tech" as in no sessions focusing on how to maximize your CoreData performance, or how to use Metal in your new iOS8 game. No talks that are technical in nature.

I make a distinction between trust and reliability. I can trust a company, even though they might not make the most reliable products.

Bugs/etc are a great way to lose my business, but not a way to lose my trust.

(what you're saying isn't lost on me, I just reserve "trust" for the situation I alluded to -- an important distinction given online privacy concerns/etc)

To counter this - installed 2.0, dropbox setup was just a matter of copying/pasting my password from 1Password (took ~10 seconds), and all my accounts/settings were there just fine.

Bugs are frustrating, but please realize that sometimes they happen despite best efforts. Lets keep small annoyances like this perspective and not say they're "ruining customer trust." Save that claim for situations like selling your data or generally being evil and untrustworthy.

I hope you reached out to the development team with a constructive bug report to help them track down your issue.

Come now, for years devs have criticized Apple for not having a proper first-party beta-testing solution. Now what might be their step into addressing that developer cry is being used against them in the typical Apple-controls-everything-FUD?

(I guess I shouldn't be too surprised, sadly...) (And, lets alt-history a bit here: had they rolled their own solution they would have been criticized for "sherlocking yet another indy product")