Post

Replies

Boosts

Views

Activity

When user goes to Settings>Their name>Subscriptions and wanna cancel the app, a "Don't go" widget is shown - is this a win back offer or a promotional offer?
When i went on to try to cancel some app's subscription, I saw this. I wanna implement the same thing for my app, but there is literally zero information online or in any docs whether this is a win-back offer, a promotional offer, or something else. And if it is a win-back offer, how to test it?
1
0
161
3w
.xcstrings catalog creates a massive git diff upon the slightest change
Every time I touch (add a key, remove a key, even add a key, then remove it) the Strings Catalog .xcstrings file, it re-renders the entire file and creates a 18 thousand line dif. When I looked closer, it changes the whitespace before colons! "version": "1.0" "version" : "1.0" it does so for every JSON node. This makes the whole feature useless, because we wont be able to see what we changed upon code review (diff is unprintable in the github interface) and every time we change a single translation, we will be stacking 18k lines diff. Not to mention merge conflicts?
2
0
247
Mar ’26
When user goes to Settings>Their name>Subscriptions and wanna cancel the app, a "Don't go" widget is shown - is this a win back offer or a promotional offer?
When i went on to try to cancel some app's subscription, I saw this. I wanna implement the same thing for my app, but there is literally zero information online or in any docs whether this is a win-back offer, a promotional offer, or something else. And if it is a win-back offer, how to test it?
Replies
1
Boosts
0
Views
161
Activity
3w
.xcstrings catalog creates a massive git diff upon the slightest change
Every time I touch (add a key, remove a key, even add a key, then remove it) the Strings Catalog .xcstrings file, it re-renders the entire file and creates a 18 thousand line dif. When I looked closer, it changes the whitespace before colons! "version": "1.0" "version" : "1.0" it does so for every JSON node. This makes the whole feature useless, because we wont be able to see what we changed upon code review (diff is unprintable in the github interface) and every time we change a single translation, we will be stacking 18k lines diff. Not to mention merge conflicts?
Replies
2
Boosts
0
Views
247
Activity
Mar ’26