Forum Discussion
MSIX AppAttach FSLogix Profile issue between packaged app versions
Has anyone experienced the following scenario: Application (PowerBI) packaged as MSIX and delivered via App Attach: Package Name: PowerBI-2.104.702.0.MSIX Delivered via App Attach to AVD FS...
Nick-S thank you for your question. The AppData root folder should be package family name based, so it works across different versions. Here it looks like FSLogix persisted app data in a version based folder. Looks like an FSLogix issue for me. One solution might be for you to change the app data folder name to exclude version number.
Aditi_Narvekar
Microsoft
MicrosoftNick-S thank you for your question. The AppData root folder should be package family name based, so it works across different versions. Here it looks like FSLogix persisted app data in a version based folder. Looks like an FSLogix issue for me. One solution might be for you to change the app data folder name to exclude version number.
Hi Aditi, Thanks for the reply, yes this turned out to be the cause of my issue:
Cause:
Used Package Full Name (PFuN) with version and not the Package Family Name (PFaN) without version
Resolution:
To upgrade the existing package , use Package Family Name (PFaN) without version; if the same Package Family Name (PFaN) IS Not used then this will result in a new package and the existing previous package settings will not migrate.
You should not put in the version alongside the Package Family Name (PFaN)
For application upgrades the Package Family Name must be consistent throughout.
The Version Control will come from the PFuN ( Package Full Name )
Cause:
Used Package Full Name (PFuN) with version and not the Package Family Name (PFaN) without version
Resolution:
To upgrade the existing package , use Package Family Name (PFaN) without version; if the same Package Family Name (PFaN) IS Not used then this will result in a new package and the existing previous package settings will not migrate.
You should not put in the version alongside the Package Family Name (PFaN)
For application upgrades the Package Family Name must be consistent throughout.
The Version Control will come from the PFuN ( Package Full Name )
