Duplicate ID error while working with Adaptation project

[SamAriekela]

I have extended a standard Fiori application using Adaptation project. I extended the view and added a new section(fragment) and deployed to FLP.   How to avoid/clear duplicate ID error while navigating back from FLP and getting back into the app?

[boghyon]

"Duplicate id" is not always caused by one specific issue. When it comes to fragments: it depends on how the fragment is created, where it's included, and whether the application follows best practices. Please share the relevant code.

[SamAriekela]

Thanks for the response. I am talking specifically for adaptation(extension) projects.  For example, to add a button to an object page, a fragment file is created and button control is added with stable id's . From my understanding, the fragments are loaded when the app ( variant)  is loaded . Now, how can I destroy these fragments onExit is my question I guess. I just gave an example for a button but there can be number of controls which are added as fragments. Hope I am asking it correctly.

[mpetrillo]

Could you solve it? I have the same problem.

[SamAriekela]

I was not able to solve it. Not a good solution but I ended up refreshing the whole launchpad on back button press for now. It worked out for us because the app is not that heavily used.

[Richie]

I have the same issue today. I am using form extensions with a oData v4 app. Within the app we use external navigation but on use of the back button to get back to my Object page I face this issue with the id of a field in my form extension fragment, It seems like a bug to me!