Axel Le Pennec
@alpennec.com
Indie app developer (Apple platforms) from Paris, France 🇫🇷
Always like that at the start of a PPO from my experience.
November 14, 2025 at 5:15 AM
Always like that at the start of a PPO from my experience.
Ah ok. You’re referring to that. I’m still on 18.7 😂
October 31, 2025 at 7:27 PM
Ah ok. You’re referring to that. I’m still on 18.7 😂
I’m not sure about the end of your post. “Power hog” 🤔
October 31, 2025 at 7:08 PM
I’m not sure about the end of your post. “Power hog” 🤔
What observable object? The macro or the ObservableObject? For the former, you still can manually check before setting a new value.
October 31, 2025 at 7:07 PM
What observable object? The macro or the ObservableObject? For the former, you still can manually check before setting a new value.
You have to run the app on a physical device, not a simulator.
October 31, 2025 at 4:18 PM
You have to run the app on a physical device, not a simulator.
Sorry, my post was maybe confusing.
It doesn’t trigger for Equatable properties when the previous value and the new value are the same/equal. So if it’s Int 5 and written Int 5, nothing is published by the Observable on iOS 26. But 5 is published on iOS 17 & iOS 18, which can impact performances.
It doesn’t trigger for Equatable properties when the previous value and the new value are the same/equal. So if it’s Int 5 and written Int 5, nothing is published by the Observable on iOS 26. But 5 is published on iOS 17 & iOS 18, which can impact performances.
October 31, 2025 at 4:18 PM
Sorry, my post was maybe confusing.
It doesn’t trigger for Equatable properties when the previous value and the new value are the same/equal. So if it’s Int 5 and written Int 5, nothing is published by the Observable on iOS 26. But 5 is published on iOS 17 & iOS 18, which can impact performances.
It doesn’t trigger for Equatable properties when the previous value and the new value are the same/equal. So if it’s Int 5 and written Int 5, nothing is published by the Observable on iOS 26. But 5 is published on iOS 17 & iOS 18, which can impact performances.
Oh ok thank you so I just need “pt”, not “pt-PT” and “pt-BR”? I now it won’t be perfect of course but I’ll optimize later.
October 24, 2025 at 12:48 PM
Oh ok thank you so I just need “pt”, not “pt-PT” and “pt-BR”? I now it won’t be perfect of course but I’ll optimize later.
I’m wondering if it’s not a way to pass App Store review more easily with picky reviewers that don’t like hard paywalls (even though it’s not against the guidelines).
October 21, 2025 at 6:23 AM
I’m wondering if it’s not a way to pass App Store review more easily with picky reviewers that don’t like hard paywalls (even though it’s not against the guidelines).