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
Describe the bug:
When developing C++ extensions for Defold, the engine sometimes fails to send a build request to the extender, resulting in a 400 Bad Request error. This appears to be related to the folder and file structure of the C++ project, rather than the source code itself.
To Reproduce:
Create a new Defold project
Add two C++ extensions to the project that I attached (ExampleExt1 and ExampleExt2)
Try to build the project
Note the 400 Bad Request error
Expected behavior:
The default engine should successfully send the required assembly to the extender and compile the project. Separately, the two extensions I created for the C++ example compile without errors.
Defold version (REQUIRED):
Version 1.9.6
Platforms:
Platforms: Windows
OS: Windows 11
Device: PC
Minimal repro case project:
Two sample projects are available: "example_good" (builds successfully) and "example_error" (fails to build). These projects contain randomly generated C++ extensions in different scopes to demonstrate the issue.
Individually, the two native extensions compile without any issues. However, when they are placed together and an attempt is made to compile them, an error occurs.
Logs (OPTIONAL):
"Async build request failed with status code 400 Bad Request{"timestamp":"2024-12-27T21:29:51.751+00:00","status":400,"error":"Bad Request","path":"/build_async/x86_64-win32/11d2cd3a9be17b2fc5a2cb5cea59bbfb4af1ca96"}"
Workaround (OPTIONAL):
No known workaround at this time. The issue seems to be related to the project structure rather than the code itself.
Additional context (OPTIONAL):
The error does not appear to be directly related to the source code.
The problem occurs in the IDE before the build request reaches the extender.
Engine version: 11d2cd3a9be17b2fc5a2cb5cea59bbfb4af1ca96
Editor version: 83536c65275c04366b704b2fd3f3d681c88b8267
Describe the bug:
When developing C++ extensions for Defold, the engine sometimes fails to send a build request to the extender, resulting in a 400 Bad Request error. This appears to be related to the folder and file structure of the C++ project, rather than the source code itself.
To Reproduce:
Expected behavior:
The default engine should successfully send the required assembly to the extender and compile the project. Separately, the two extensions I created for the C++ example compile without errors.
Defold version (REQUIRED):
Platforms:
Minimal repro case project:
Two sample projects are available: "example_good" (builds successfully) and "example_error" (fails to build). These projects contain randomly generated C++ extensions in different scopes to demonstrate the issue.
Individually, the two native extensions compile without any issues. However, when they are placed together and an attempt is made to compile them, an error occurs.
Logs (OPTIONAL):
"Async build request failed with status code 400 Bad Request{"timestamp":"2024-12-27T21:29:51.751+00:00","status":400,"error":"Bad Request","path":"/build_async/x86_64-win32/11d2cd3a9be17b2fc5a2cb5cea59bbfb4af1ca96"}"
Workaround (OPTIONAL):
No known workaround at this time. The issue seems to be related to the project structure rather than the code itself.
Additional context (OPTIONAL):
The error does not appear to be directly related to the source code.
The problem occurs in the IDE before the build request reaches the extender.
Engine version: 11d2cd3a9be17b2fc5a2cb5cea59bbfb4af1ca96
Editor version: 83536c65275c04366b704b2fd3f3d681c88b8267
examples.zip
The text was updated successfully, but these errors were encountered: