We are using Abp in our company with a custom react frontend (this was started before Abp's react module was added). Recently we updated from v10.0.0 to v10.1.1 and there's a new required property UpdateProfileDto.AppName. This caused one of our forms to break, the fix is simple but I wasn't able to find any documentation on when/why this change was made.
I would like to know where I can find a PR/Commit/issue/discussion/release for this since the code for this class is not available in the Abp public repo and I'm not able to use the file as a starting point.
7 Answer(s)
-
0
UpdateProfileDtobelongs to the Account module (not Identity). ABP moved the whole profile API (IProfileAppService+ related DTOs likeUpdateProfileDto) from Identity to Account earlier (so it’s normal you don’t find it under Identity sources).For the specific change you hit (
UpdateProfileDto.AppNamebecame required / newly required in v10.1.1): I can’t verify a public PR/commit/discussion for that change with the tools available here.- I searched the indexed public ABP GitHub sources for
UpdateProfileDto/AppNamebut found no occurrences, which indicates the change is likely in a part not included in the indexed open-source repos (or in a product/module repo not available here). - So I can’t provide a verified PR/commit link for that exact change.
- I searched the indexed public ABP GitHub sources for
Practical guidance (so your custom React client won’t break again on such DTO changes):
- Treat ABP’s “My Profile / Update Profile” endpoints as versioned contracts and regenerate client proxies on every upgrade (even if you don’t use the official React module). This catches required-field changes early.
- When calling the profile update endpoint from your React UI, always send
appName(typical values used by ABP UIs are UI identifiers like"Angular", etc.). In your case, pick a stable constant for your frontend, e.g."React"or your product name, and keep it consistent.
Where you can reliably track some profile API history:
- The (older) official migration guide that documents the module move (Identity -> Account), including a reference PR (but that specific GitHub PR link is not accessible from my URL checker right now).
Links I can confirm are reachable:
- https://abp.io/docs/latest/release-info/migration-guides/abp-5-0
- https://abp.io/support/questions/1404
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hello,
The AI answer didn't help, I would like to find out why this change was done.
Addressing the AI's suggestions
- Treat ABP’s “My Profile / Update Profile” endpoints as versioned contracts and regenerate client proxies on every upgrade (even if you don’t use the official React module). This catches required-field changes early.
- We don't use the client proxies, as i stated in the first line of my original post we use a custom react frontend as the project was started before the react module was available.
- When calling the profile update endpoint from your React UI, always send appName (typical values used by ABP UIs are UI identifiers like "Angular", etc.). In your case, pick a stable constant for your frontend, e.g. "React" or your product name, and keep it consistent.
- It was not a required property in the dto before so we didnt send it. I also don't fully understand what the purpose of the value is and was hoping by reading some discussion around the change I would understand it better
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
The
AppNameproperty was added toUpdateProfileDtoin v10.1.0 as part of a feature that requires email confirmation when a user changes their email address on the profile page.When
Abp.Identity.SignIn.RequireEmailVerificationToRegistersetting is enabled, updating the email triggers a confirmation email with a verification link. TheAppNametells the system which application URL to use when generating that link (e.g., MVC, Blazor, Angular), since different frontend apps may have different base URLs configured viaIAppUrlProvider.To fix this, just pass an
AppNamevalue when calling the profile update endpoint. You can use"MVC"or any name that matches your app URL configuration. For example:{ "userName": "john", "email": "john@example.com", "appName": "MVC", ... }If you have a custom app URL configured in
AbpAccountOptions, use that name instead. Otherwise"MVC"works as the default.Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Is there a way to get a more detailed release notes for the releases? The releases section of the site doesn't mention the email changes you mentioned. https://abp.io/qa/questions/10598/3a20a1a7-0c56-f390-3844-f409acb8f0cd
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
You're right, this change should have been documented in the release notes. Currently our release notes focus on new features and may miss breaking changes like this.
The reason you hit this issue is that you're using a custom React frontend. Our official templates and UI projects (MVC, Blazor, Angular, React) are updated to match these DTO changes automatically with each release, so users on those don't notice the change.
I've noted this as feedback — DTO contract changes that break existing API calls should be listed in the release notes or migration guide, especially for users with custom frontends.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Thank you, will keep an eye on the release notes here as well as github for future releases before we update to it
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
