After purchasing a single license for iPad v2 photo & designer, I purchased a universal license from the affinity store.

[tsudatomo]

After purchasing a single license for iPad v2 photo & designer, I purchased a universal license from the affinity store.

Then, every time I launch iPad Photos and Designer, I am prompted to register the app with my Affinity account.

When I perform the operation for registration, a message will be displayed to the effect that you have successfully registered with an existing affinity account.
However, the next time I launch the app, I am again prompted to register the app to my account.

By the way, I can use the app itself, so it's not a fatal problem, but it's annoying to see it every time I start it up.
Please tell me how to solve it.

Edited January 1, 2023 by tsudatomo

[SFurniss]

@tsudatomo

Here's a link to an article talking you through license activation. If you need any further help with this please email affinity@serif.com
 

https://affinity.serif.com/learn/in-app-licence-activation/ 

[blackjackroberts]

I have the same issue as tsudatomo I have the Apple store version of Designer 2 and purchased the Universal license now my iPad version of Designer 2 hangs when i try to log in to my serif account, the app still works without being logged in and the other Universal license apps login fine. 

[emmrecs01]

@tsudatomo @blackjackroberts

I think we need @SFurniss to comment definitively on this but I wonder whether the fact you have TWO licences for ONE of the Affinity apps (the single licence and the universal one) is causing a problem for the licensing process to successfully "allocate" at least one of the apps to your licence.

Could the problem be resolved if you request a refund for the single app licence and thus have it "removed" from your account?

[SFurniss]

@tsudatomo @blackjackroberts

Based on the email addresses linked to your forum accounts, I can see you have both successfully registered your software previously. If you click off the registration screen you'll be able to continue working with the software. Our developers are aware of this bug and have plans to fix it in a future update.