Unsupported file type

[Kultie]

Hi,
When I update Addressable from 1.13.1 to 1.16.10 and rebuilding asset for testing I encountered this issues

Build Task GenerateLocationListsTask failed with exception:
Cannot recognize file type for entry located at 'Assets/AddressablesResources/Portals/GameData/Portal_IconGame_Lobby_1.tpsheet'. Asset import failed for using an unsupported file type.

version 1.13.1 worked fine but at that version on android build content update not working for me because of CRC miss match and catalog not updating resulting in old scene data, scriptable object ,…

Anyone know what version is really stable at this point?
What kind of file type that addressable supported?

If anyone know how to resolving the CRC miss match and catalog updating issues please let me know.
When I test with simple project with scene and some game object the update system work fine but in the main project it’s really not reliable
Edit: Can not update bundle on mobile
using this I’m able to resolve the update content problem. Since content in library folder often get ignored so I add a little script to change content of the settings.json file before build

[AlekzFateJumper]

I’m having the same problem here. I used to send a .dat and a .xml files and now I’m also getting this warning that the location will be ignored.

UnityEditor.GenericMenu:CatchMenu(Object, String[ ], Int32) (at /Users/bokken/buildslave/unity/build/Editor/Mono/GUI/GenericMenu.cs:119)

[Treyrannosaurus-Rex]

I’ll flag for the team to have a look!

[davidla_unity]

I think this can be worked around if you check the “Ignore unsupported/invalid files in build” box on the AddressableAssetSettings object. The file won’t be the build, of course, but it should stop the build from failing. Let me know if that works.

[AlekzFateJumper]

@davidla_unity

I think this can be worked around if you check the “Ignore unsupported/invalid files in build” box on the AddressableAssetSettings object. The file won’t be the build, of course, but it should stop the build from failing. Let me know if that works.

I’ve done that, but the main idea is for this file to be updatable by addressables.

[cassideedle]

Hi there, same question.

How do we register file types (file extensions) that Addressables doesn’t natively support? So for example, .txt files seem fine - but .js and .map files don’t.

I tried creating a ScriptedImporter to register a .js or .map file - but that generates the following error:

---

The scripted importer ‘JavascriptFileImporter’ attempted to register file type ‘.js’, which is handled by a native Unity importer. Registration rejected.

We can of course bundle those files into bundles or binaries - but we were looking for a way that would allow us to just the raw files into Addressables.

Thanks!

[HECer]

Same issue here, any news about it?
The custom mp4 file (containig more information, cannot be converted) needs to be an addressable too for updating the game. How can i achive it? It always throws unsupported file. I can’t write my own AssetImporter because mp4 has already a native one.

[RedVonix]

I’m seeing this exact issue with .prefab files (unsupported file type), which I imagine should be supported by the Addressables system.

[RedVonix]

In addition - I’m also receiving ‘unsupported file type’ for .mat files. Both .mat and .prefab are unsupported? That doesn’t seem right at all… Major bug?

[unity_shane]

@RedVonix

I’m seeing this exact issue with .prefab files (unsupported file type), which I imagine should be supported by the Addressables system.

Which Addressables version are you seeing this in? This definitely sounds like a bug - any chance you could send a bug report with a project that reproduces it? Prefabs and mat files should both be supported.

@HECer

Same issue here, any news about it?
The custom mp4 file (containig more information, cannot be converted) needs to be an addressable too for updating the game. How can i achive it? It always throws unsupported file. I can’t write my own AssetImporter because mp4 has already a native one.

If you’d like to edit the AssetImporter you’re free to do so by pulling the addressables package folder from your library directly into your packages folder and then editing the file directly. The only down side to editing your package like this is that whenever Addressables updates you’ll have to copy over your changes manually since the package manager doesn’t have any built in way to diff your custom package with the new version. Still, if you have custom mp4 files that you want to be included in your build, that is an option for you!

[MadboyJames_1]

I am having this issue on an ubuntu github actions server. It works fine locally, but on ubuntu I get
“Cannot recognize file type for entry located at ‘Assets/Art/Textures/UniqueProjectilesVol1_8x8_4K.PNG’. Asset import failed for using an unsupported file type.”

This works fine on my local windows machine, but not on ubuntu. Any idea why this might be happening or how to fix it?

Someone suggested it may be due to windows not caring about case, while ubuntu does. If this is the issue, how would I fix it?

[MadboyJames_1]

Figured it out: Removing the underscore from the filename allowed the addressables to build successfully.