Translating entire Storyline files with an alternative method

Like Manuel and Jürgen, I've developed companion apps for Storyline and Rise 360 (due to forum rules, I can't mention these by name as it could be considered self-promotion).  I tested my latest app using Manuel's files (thank you for posting these!) and I think I have a better understanding now of what is happening.

Here are the steps I took to get to my below hypothesis:

• I took Manuel's first Storyline file (English audio) and replaced the audio with my app.  I then published the course and the replacement audio worked as expected (it was not the original audio but the replacement audio I chose).
• I then opened Manuel's second file, noted the French replaced audio, made no changes and published immediately.  The audio that played was the audio I replaced in the first file - not Manuel's English file or French file that appears on the timeline.
• I went ahead and replaced the audio with my app on Manuel's second file with a copy of the French audio that I named differently.  Again, the audio that played was the audio I replaced in the first file.
• And then to close out testing, I went back to the first file of Manuel's, replaced the original file's audio with my app again and... same result.  The very first audio file I used played and not the new audio. 

Here's my hypothesis in what might be happening in this specific situation.  Please jump in and let me know where I'm wrong in my assumptions:

• The Storyline application uses an internal settings file.  It is not a cache per se but rather a table that stores a unique ID for both external assets (audio, image, video) and internal assets (textbox, button, etc.) added to the application as a whole and not a specific .story file.  One cannot simply delete the cache to 'cure this problem' - this internal file also stores application settings, etc. so you likely wouldn't want to delete it even if you could.
• The unique ID is likely a checksum of the file from my simple testing.
• Storyline seems to fetch a new ID only when the replace media function is called by the user.  With the new ID added to the internal settings file, the course publishes as expected (the replaced audio is what you expect to see in the published version of the course)
• Items with this specific ID seem to be 'timeline bound' - it has to be placed on the timeline to get an ID.  Captions do not live on the timeline but rather are added to another object so doing a replacement with my app has no problem.
• The ID is only 'checksum unique' and not truly a new ID created each and every time an asset is added.  If that were the case, my experience above should not be repeatable (and perhaps it isn't but with the testing I did, it seems so - Manuel had the perfect example because the second file is a direct copy and not a new Storyline course.)

I think part of the solution to the problem would be to refresh the internal settings file.  I can't think of a way to do this in how Storyline is programmed today.  It would have to be an internal programming change.  The developers wouldn't want to do the refresh often though because there would likely be a significant performance hit as every asset (external and internal) has an assigned ID.

I hope this all makes sense and leads to further discussion.

Thor