87
points
You can't save it to iCloud files and open it
You can't use the share button
You can't open an .ics file on your browser and add to the Calendar
You can't open the Calendar app and import from there
Apparently you can only add it to the Calendar if you receive the file as an attachment in the native Mail app
https://discussions.apple.com/thread/253646020
I thought the whole idea behind iOS was that "it just works"
Solution: Wait until it syncs to the Mac, select the event, right-click -> Email Event, in the mail pick the .ics and save locally (then discard the email), then share that file via the messenger.
Yeah, I mean, sharing an event, a rare and complicated feat.
And I wanted to create a common calendar so one can set reminders for her (and all of us) about medical appointments, medicines and stuff that we all could manage from our phones, wheter Apple or Android, or my computer, via a web browser, caldav or whatever. I imagined that would be second nature, after all it's just a calendar, right?
Well, it's 2023 and you can't do that because reasons.
They're getting better at "back-porting" stuff from real computing platforms, like Files (which can even connect to SMB shares, though last time I checked only using protocol version 2 and with the least helpful of error messages when it fails ... why?!?!?!?!).
But there's still a long, long way to go if they ever really want iOS to succeed macOS.
At the current state of affairs the only way to make the iPad a full computing platform is using macOS sandboxes (which I had expected to come with the M-processors).
There's a lot of shit I don't appreciate about Android, but setting as many timers as you want is a total no-brainer.
Having multiple timers running is inelegant and sometimes confusing. So instead of giving users any agency in that situation, they just ban the very concept as a whole.
If they feel enough pressure, and they can come up with a satisfactorily simple UX, they will usually eventually fix the hole.
Of course, many apps on the app store offer this feature.
The main annoying part is iOS PWA's kill their service workers when off screen even when explicitly told not to via the `waitUntil` command, so you need to have a server running which handles keeping track of the ongoing timeouts and calls the push notification endpoints accordingly.
Code for that is here, https://github.com/JacksonKearl/push-simple. There's a Dockerfile, currently deployed via fly.io.
Funny that I provide a fully working code sample of how to do what the parent wants, explain the caveats associated with it, and get downvoted because Apple crippled their service workers... ok then, Hackers.
You need to choose the right Content-Type on the web server for the ics file delivered to iPhone, “text/calendar”. Safari doesn’t care what file extension the file has if the Content-Type is right.
As with all things and in all things, remember that it's just marketing that one chooses to believe.
That had never been true. OSX and iOS/iPadOS have always had their warts and the only people that denies that were hopeless fanboys wearing rose-tinted glasses.
It's software is generally well integrated within its own ecosystem, which makes a lot of interactions much better compared to the alternative... But only if you stay within the tiny confines of what Apple deems an acceptable workflow, which manually importing ics files clearly isn't.
You can do this via a shortcut and that is sadly how I have handled it for years now.
It means the Android operating system does not implement the DHCPv6 protocol.
> How is it impacting users?
Users of Android devices will be unable to obtain a managed IPv6 address configuration, other configuration, or request an IPv6 prefix (read: prefix, not address) via DHCPv6 Prefix Delegation.
> Are they crying out about it on support forums for the past several years?
For at least 10 years now[0].
[0] https://issuetracker.google.com/issues/36949085
Mobile devices typically (read: by default, and if they don't people will berate them for not caring about privacy) randomize the DHCPv6 DUID and MAC address used for the connection, meaning that one might as well just assign a random IPv6 address from the given prefix. Which is exactly what you get without DHCPv6.
The only people demanding DHCPv6 in Android are network admins still under the strange illusion that DHCP somehow gives them some kind of "management", "accountability" or "logs". They didn't get the memo that they will still have to correlate their 802.1x auth with the current device mac and IPv6 addresses in use, which is in no way whatsoever helped by DHCPv6.