New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown bug #398
Comments
And how is this a bug? |
@khaled-0, look at the path, it's about built-in libraries. That's not supposed to happen, though one could achieve that by using a Developer Tools option. Can you try clearing the app cache, and if that doesn't work, the app data? |
This comment was marked as spam.
This comment was marked as spam.
So for some reason it expects built in libraries in data/data/...cache/libs/libs/ |
Some? That's intended, see commit ebbc8f4. I'm sure it's also extracting built-in libraries to that location, since it worked on my device. I'm guessing this is another bug similar to the older …/res not found bug, where the ZIP file wasn't fully readable by some devices. |
What's the point if you have all the libs extracted in |
Wait no, so for some reason it doesn't try to extract the libs after first time |
They aren't getting copied over to the cache directory, but instead, getting extracted there. Since deleting those files isn't fatal and Sketchware Pro can extract them again on its own, using the cache directory is better, for example for users who want to quickly make some storage space free. |
That's the thing |
wait bruh lol |
Must be because dexs.zip and libs.zip still get extracted to filesDir, not cacheDir. |
No And it just instantly completes the Extracting part when building |
Weird, they did for me after I deleted the entire libs folder in the files directory. |
Should have been fixed with 6bc31f7. |
Even tho it's marked as fixed and it works |
I downloaded the latest action, and when I run the program, it always shows me a message to create a res folder in the local libraries, while in previous versions this message was never displayed to me.
The text was updated successfully, but these errors were encountered: