PupperPost provides a super-nice experience for #blogging: from idea to a post you own in no time and without fuss, easily customizable, extremely nice UI on all Apple platforms, and especially great on the Mac.
When I'll get around blogging more, which is something I really want to do 🥺, PupperPost will be my home!
If I were Apple I would be near the point where I’d scratch the CTF, open side loading to the point that alternative app stores aren’t even needed, preinstall all alternative browsers and pull Apple Music from the EU.
Then I’d raise iPhone prices 5% in the EU markets as a cost for software customizations for #DMA.
#Swift LPT: I’ve often seen iOS apps where customising icons is possible, but the first time it requires a reboot of the iPhone to show the change; then, any subsequent variation is immediately applied.
watchOS should be able to reliably wake up the phone, if reachable;
If not reachable, it would be reasonable for the watchOS app to inform the user it cannot work atm;
What I’m not sure about is how long the back & forth would take, considering the phone operation is already asynchronous and depends on networking (let's say, an average of 5s for the operation itself to complete).
-> Can I assume the blob would be messaged back right away in most cases?
@cdf1982 I found out that the first WCSession.sendMessage call often returns a .notReachable error. So I try up to three times with a delay of 500ms between each call. The second call usually works.
Here's a gist of my code. It contains the code to retry the request and a "Request" class, which is a mechanism to cancel the retries:
I don’t know if I’m more annoyed by the fact that I was able to avoid it this far and now I got it, or that I’m testing positive the morning I had my vaccine scheduled.
Sore throat, low fever, I’m fine.
@santiago A positive outlook is important! Maybe on everything else but this, if I could choose, but hey, I've never felt really bad so, I should really stay positive ;)
If you look at this sample project, you'd say it works. Truth is, dots lie!
When rows changes, “real” views aren't redrawn!
So, a grid of items has duplicates: those not updated by the 1st ForEach.
And that’s ForEach expected behavior reading iOS 13b5 release notes: “you shouldn’t pass a range that changes at runtime…. displays views according to the initial range and ignores any subsequent updates to the range”.
@cdf1982@Alexbbrown Can you change the Gist's code to something that shows what is breaking, and where to click? I just now read that you wrote "dots lie", so the fine-looking example with the colored circles seems to not show the problematic behavior?
@ctietze@Alexbbrown You're absolutely right. I need to figure out a different experiment example, because mine relies on RTSP streams and is hardly shareable. I'll think of something with images or some other view.