You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, in the attached project, _customize_scene() method is never called.
Interestingly, if the included plugin's aar archive files are removed and replaced with dummy files, then the export mechanism starts calling the _customize_scene() method.
Steps to reproduce
Open attached project in Godot Editor
Install Android export template from Godot's Project menu
Select Android export preset and export debug
Check output tab & notice that _customize_scene() is never called (addons/SharePlugin/ShareExportPlugin.gd)
Remove addons/SharePlugin/bin/debug/SharePlugin-3.0-debug.aar and addons/SharePlugin/bin/release/SharePlugin-3.0-release.aar & replace with dummy files, & notice that export fails, but _customize_scene() method is called.
Uses a cache for the converted files if nothing changes, so this work only happens if a file is modified.
For large projects it makes sense to speed up the export process. Otherwise, editor_description could be adjusted, e.g. write timestamps there to force _customize_scene.
Tested versions
Reproducible in 4.3.stable
System information
Android 13 - Godot v4.3.stable - Windows 11 dev environment
Issue description
The documentation states:
However, in the attached project,
_customize_scene()
method is never called.Interestingly, if the included plugin's
aar
archive files are removed and replaced with dummy files, then the export mechanism starts calling the_customize_scene()
method.Steps to reproduce
_customize_scene()
is never called (addons/SharePlugin/ShareExportPlugin.gd
)addons/SharePlugin/bin/debug/SharePlugin-3.0-debug.aar
andaddons/SharePlugin/bin/release/SharePlugin-3.0-release.aar
& replace with dummy files, & notice that export fails, but_customize_scene()
method is called.Minimal reproduction project (MRP)
customize-scenes.zip
The text was updated successfully, but these errors were encountered: