The loading failure occurs because file systems on mobile platforms often handle character encoding differently than the development environment. By default, your script might be using the literal file path as the internal identifier, which breaks when special characters are misinterpreted during path resolution.

To resolve this, follow these steps:

1. Select the AddressableAssetSettings asset in your project.
2. In the Inspector, locate the Internal Id Mode property.
3. Change the value from Full Path to GUID.
4. Open the Addressables Groups window.
5. Select Build > New Build > Default Build Script to regenerate your catalog with GUID references.

Changing the mode to GUID ensures that the system references the asset by its metadata-linked GUID instead of a string-based file path, making it immune to character encoding discrepancies on various operating systems.

Additional Tips:

• Avoid using special characters in filenames whenever possible to ensure cross-platform compatibility.
• Ensure that the Include GUIDs in Catalog checkbox is enabled if you are using manual GUID referencing.
• Clear your Addressables build cache before creating a new build to avoid stale path data.