Product not updated properly and folder name change

Summary

It has happened many times already but when I update a product on FAB, sometimes I receive a confirmation that the update is done but nothing was changed, or worse some folders are renamed.

The first time the main folder was renamed creating a compile error in my tool and I got ± 3 one stars in a week (my tool was available for a year now and I had one 1 one star before that moment)
The second time and third times someone asked for support for a fixed bug.

Every time I double-checked the Google Drive and the link provided. I also downloaded the same file I sent to validate that the error is not on my end.
I’m not sure how those kinds of errors can happen but please, we work really hard to build some quality content,t and it’s hard to see that we get those one-star for mistakes that are not even on our end.
Worst, we don’t have text reviews so we can’t even react when it happens.

What type of bug are you experiencing?

Publishing

Steps to Reproduce

As described above, it is on FAB’s end.

Expected Result

When we update, the product is updated as it is with no custom change made by FAB

Observed Result

The product is either not updated, or updated with errors.

Platform

Web

Operating System

Web

EMP-15058 has been created and its status is ‘New’. This is now in a queue to be reproduced and confirmed.

Thanks Michael - we’ll take a look.

2 Likes

Make sure to provide a new url storage link and the project name+description is different. Plugin not updating files - #3 by Arodi007

Not updating the asset files at all if the file and version is the same would be the best. It can be very time consuming to have to check again all file versions after a minor update to the store page for instance…
Having a similar system as on UEM where you have to explicitly request a file update would be the ideal solution.

Yes, I have one folder per update and they are unique every time

@Mick129 @skfabby We got a seemingly similar problem and I want to verify that we are seeing the same thing, and that I’m doing things correctly.

Out plugin in named AGXUnreal. When publishing to Fab we submit a link to a Zip archive containing a single root folder named AGXUnreal, which in turn contains the AGXUnreal.uplugin file, the Source folder, and so on. We depend on the plugin being placed in a folder named AGXUnreal when installed by the user. This worked as expected on the Unreal Marketplace but after the migration to Fab the folder created on the users’ machine is no longer named AGXUnreal but AGXDynamd67353865a0dV8. I can theorize where the first bit of the name comes from (the first few characters of the title of the plugin’s product page) but the rest seems like random numbers.

Is there a way to control the folder name when our plugin is installed?