Hi @FlexSolution! Please, specify the project-type and version you are using.
I'm currently playing around with editions - to be honest: I was a bit confused about this screen as well, when I tried changing some values. Obviously, editing an edition that is in production and already has tenants assigned is not a good thing to do - so I can perfectly understand the way it is implemented.
Still, I think it would be better to just disable the input fields instead of not showing them at all. Maybe adding additional information about creating a new edition and moving tenants instead of editing an existing edition!?
What do you think?
@FlexSolution that would be even better : ) Thanks for your comment!
Hello @ismcagdas!
I was able to solve the problem - which was just me not understanding how feature declaration works :D
Sorry, I wanted to post an update here but then I forgot about it ...
Anyway, thanks for your reply!
To be more precise: If you are using the same authentication service for both of your clients, your clients will need to identify themselves additionally. That way, your authentication service can then check for the specific user-property (mentioned in my post before) and then decide whether to ignore or not.
I think, you would have to extend the user-class and add a property that indicates whether the user was created on mobile application. Your web-application must then check for this property and ignore authentication attempts by mobile-application-created users.
Sorry, I just forgot to apply current database-migrations (Upgraded_To_Abp_v4_2_0) ... my bad ...
Finally, I was able to figure it out : )
Logs didn't help much, though. Except for telling me that it might not be a problem with the application itself (since I couldn't find any messages about errors). Anyway, I learned about logging in Azure and how to analyze it, which is nice.
The fact that there was just one service method failing (and only for host users) got me thinking, though: What if there is something wrong with the data that I'm trying to request!?
And there it was, right in front of me all the time: a referetial integrity issue :D
I deleted the entry that was causing the problem and now everything works fine. I just need to make sure this doesn't happen again.
Closing this now - thank you for trying to help me!
FYI, I can trigger this error using postman.
Calling service as Host:
Calling service as Tenant:
