Asset Integration: Image Assets Not Rendering in Android Build

[elcoosp]

Summary

While integrating Lynx into an existing Android project using custom templates, image assets fail to render in the production build despite successful compilation and bundle generation. Current implementation uses a workaround for asset copying that appears insufficient for proper asset resolution.

Implementation Details

1. Base Setup

   • Created custom template based on documentation

   • Followed Lynx integration guide

   • Successful compilation for Android (Java/Kotlin)

2. Bundle Generation

   • Integrated create-rspeedy template

   • Implemented custom rsbuild plugin for asset copying to app/src/main/assets

3. Testing

   • Build artifacts generated successfully via test script

   • App runs on device but fails to render image assets

   • Screenshot:

Current Issue

The manual asset copying solution appears incomplete, specifically regarding:

• Proper asset path resolution in production builds

• Potential misconfiguration of asset URL prefixes

Questions

1. What is the recommended approach for asset management in custom Android integrations without Lynx Explorer?

2. Should output.assetPrefix be configured differently for native packaging?

3. Are there established best practices for:

   • Asset directory structure in hybrid projects

   • Build-time asset processing

Additional Context

• iOS implementation not yet attempted

• Current workaround focuses on Android-first implementation

• Willing to provide build logs/asset directory structure if helpful

---

Request
Seeking guidance on proper asset handling patterns and configuration adjustments needed to resolve rendering issues while not relying on lynx-explorer.

[elcoosp]

Forcing inlining did the trick.

So If I am correct it's not expected to have any static assets (images) inside android/{{project_name}}/app/src/main/assets, I should only copy the main.lynx.bundle in this folder and use a static web server for static assets.

[NusryNizam]

Seems like it couldn't resolve absolute paths.

@elcoosp thanks. your solution worked.