![]() ![]() Wonder how many devs have to add these for Apple to I don’t know fix the problems or at the very least publicly acknowledge them. ICloud errors seem to have really increased over the last couple of days. ![]() ![]() Well, add me to the pile of ppl making an iCloud status dashboard for my app Others, though, have reported losing records and files. As far as I can tell, eventually all my data did sync. My devices haven’t reported any error codes, but iCloud Drive and Photos have been particularly unreliable and slow for the last week or so. It seems it’s happening to other apps as well. This issue is not apparent to us and we’ve escalated the case to Apple Technical Support team for investigation. The error typically gets resolved as GoodNotes automatically retries, but we’re getting many reports of the error lingering on, causing sync failures. HTTP 503 is a temporary error code (“Service unavailable”) indicating iCloud servers aren’t responding correctly to requests from your devices. Why am I not surprised?ĬSS iOS iOS 15 Mac macOS 12 Monterey Open-source Software Safari WebKit And yet when it happened in this case, the reaction in some quarters was to complain. I sure wish I could crowdfund features that Apple doesn’t care about in my favorite apps and have Apple add them to its code base! But only in very particular circumstances-when there’s an open-source project at the core-can it happen. Of its own volition, Igalia decided to experiment with the idea of letting the web community (the “crowd”) vote for implementation of a missing browser feature with their wallets (the “funding”). In fact, all of those assumptions get things almost exactly backwards - which is understandable! It’s what we expect from our experience of how the web has developed since at least the late 1990s. They didn’t even ask Igalia to implement :focus-visible, and then Igalia decided to crowdfund the work. Nobody at Apple asked Igalia to crowdfund anything. Nobody at Apple asked the crowd to fund anything. Floatplane COO Luke Lafreniere has ongoing issues with getting a media network app already on the App Store through review, and time after time struggles despite carbon copying solutions adopted by big and successful apps on the App Store, to the point of copying UI wording verbatim.Īntitrust App Store App Store Rejection Apple Business Dating Apps In-App Purchase iOS iOS 15 Legal NetherlandsĪpple Did Not Crowdfund :focus-visible in SafariĪ few people, including Jen Simmons, gave credit to Igalia for implementing :focus-visible by means of a crowdfunding project (more on that in a moment). Time after time, Apple has either completely missed or blatantly ignored what makes a sensible application for developers and users, focusing on what draws in more money or tightens the regulatory noose.Ī recent installment of the ongoing Floatplane App Review saga is instructive. What you can’t do is argue these things and then turn around and say that it’s all fine when Apple is doing it to developers. They put a price on criminal behavior, and if the gains from committing those crimes exceed the cost of the fines, there’s a base hyper-rational calculus that says the company should continue to break the law. Relaxing Anti-Steering Rules for Reader Apps.Dutch Anti-Steering Ruling for Dating Apps.StoreKit External Purchase Entitlement for Netherlands.Or they could just pull dating apps from the App Store in the Netherlands. It must be really frustrating to roll out an entire plan only to be completely at the whim of a reviewer - err, regulator - to find out whether it sufficiently meets a set of vague criteria.Īpple could just write them a check for €50 million now, from the company’s spare-change-under-the-sofa account. Providers must be able to choose both options. For example, Apple seemingly forces app providers to make a choice: either refer to payment systems outside of the app or to an alternative payment system. That, too, is at odds with ACM’s requirements. In addition, Apple has raised several barriers for dating-app providers to the use of third-party payment systems. At the moment, dating-app providers can merely express their ‘interest’. The most important one is that Apple has failed to adjust its conditions, as a result of which dating-app providers are still unable to use other payment systems. As a result, the ACM has hit Apple with an initial 5 million euro fine as a consequence, and fines will continue to be assessed at 5 million euros per week up to a maximum of 50 million euros until Apple complies.Īpple has failed to satisfy the requirements on several points. The Dutch Authority for Consumers and Markets (ACM) has ruled that Apple’s plan to allow App Store dating apps to use third-party payment methods for in-app purchases does not sufficiently meet the requirements of a previous ruling. Netherlands Rejects StoreKit External Purchase Entitlement Plan ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |