We’ve investigated this issue and were not able to reproduce it on our end. I noticed that you already have some translations populated in your table shortly after this report was posted. The coverage issue might be occuring because “Capture text from experience UI while users play” setting (Automatic Text Capture) was not active at first. This setting is what automatically detects and adds new translatable strings to your table.
If you’re still seeing 0% coverage today, please let us know, and we’ll investigate further.
Thanks for the update - I just took a look at your localization table and saw that automatic translations have been populated. For example fish bone was translated to “Hueso de pez” by automatic translation on 4/16. Can you check to see if you are able to see any automatic translations? Thanks!
I proceed to try pressing all of the button i see in this page (even the Delete Table button) and nothing would allow me to proceed because of this unknown table error
Interesting. We checked your localization table on our side and everything looks normal. To further investigate, you could try adding me as a translator to the experience so I can inspect the table call better from our side.