By the way, Dashboard thinks all went well. I tried downloading the zip file, and it does not contain the localization file (localization.lua) at all, while all other files are present
Date Priority Message Revision
1 hour ago Low Request completed. --
1 hour ago Low Completed revision: 08a6f695f199fd898f6826a99b7496e182e14791 08a6f695f199fd898f6826a99b7496e182e14791
1 hour ago Low Processing revision: 08a6f695f199fd898f6826a99b7496e182e14791 --
1 hour ago Medium Revision 76d33362c05958f7cb2a5f0f2c1be7b9920600e9 with tag 0.1.0-Beta6 has already been processed. 76d33362c05958f7cb2a5f0f2c1be7b9920600e9
1 hour ago Low Processing revision: 76d33362c05958f7cb2a5f0f2c1be7b9920600e9 --
1 hour ago Low Processing request. (attempt 1) --
We're still manually approving files, yes. We're working on getting our schedules rotated around for better coverage - we try to keep the wait times low during our available hours, but unfortunately things still get a bit busy from time to time.
As for the localization, it's likely that our CDN is caching the file before it gets processed, which is why when you download it from your backend, you're not seeing the localization file.
I'll ask to see if this is the case, but checking the file from our end, it all looks good - this would be the file served to users. If it is being cached, this shouldn't affect any other users aside from you.
Mixed feelings: while I deeply appreciate and respect your dedication, I cant but ask what went wrong , because I am sure that manually fiddling with all uploaded files was not your plan A (nor the B one, probably).
I also understand that you are quite busy right now, so never mind if you cant find time to answer this question.
The token-replacement aspect of localization system was previously only available to people using the packager for their projects; as soon as the file was packaged, the localization replacements were in it. Now, anyone can use the system which means - for projects which have the localization system enabled - a processor which is completely separate from the packager runs on the zip. This is why we're "fiddling" with files after upload.
The unfortunate aspect of this is that these files are immediately shown to and available for download to any member of the project with the Manage Files permission, despite the fact that the processing has yet to be done. Users will only ever see the file after its status has been set to Approved, so there is no chance that they will receive an incomplete build. There is a ticket in with the developers to not show these files to anyone until they've been fully processed.