Fredia Huya-Kouadio
Fredia Huya-Kouadio
> The one thing I'm uncertain about: this is also moving custom export templates into advanced settings for all platforms. Should this be included in this PR? Or, a separate...
> > The one thing I'm uncertain about: this is also moving custom export templates into advanced settings for all platforms. Should this be included in this PR? Or, a...
> can't download and install export template from editor and does not seem to recognize this artifact template That's expected as there's no export template on the server for custom...
> My main concern is with the addition of the apksig library, which seems to be a very big dependency (most of the 30k locs of this PR), and a...
> > When compiled, this PR seems to grow the Android build template by ~4mb (`66.7mb` for android-template-arm64 vs `62.9mb`); one option to remove the impact would be to move...
> I tried it worked but it doesn't supporting gradle build........?????? Why???? @Loki76222 We're still investigating how to support gradle builds for the Android editor.
> Testing master ([292e50e](https://github.com/godotengine/godot/commit/292e50e17e3f6e2509d3178a00204f964a907460)) on a pixel4 and I get the same splash screen with the compatibility renderer and with the mobile renderer. In both cases it is wrong, but...
> Is this a new issue with beta 1? Have you reproduced this on earlier dev builds? The issue was reproducible in earlier dev builds.
> If this is a regression, it would be good to pinpoint when it appeared. But if the issue isn't reproducible without #92965 as the splash screen doesn't even work,...
@BastiaanOlij A quick workaround until the issue is fixed is to unplug and replug the Quest device.