Forum Discussion
Issue Deploying to tenant app catalog
JaydenMarquardt Then there maybe a space/dash/underscore in the file name of one of the assets. When you deploy with --ship, it includes all client side assets in package.
So, check all the images/css/js/ts/tsx/fonts assets in your solution and remove space/dash/underscore in their names? Did you check this as well?
In one of our solutions there was spaces in image file names which was causing this issue.
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
JaydenMarquardt I have faced this issue recently. Try this:
1. Create a new folder at top level in any drive (C or D drive) without spaces or dashes--> Move project solution into this folder. Then use below commands:
- gulp clean
- gulp build
- gulp bundle --ship
- gulp package-solution --ship
2. Remove dashes/spaces/underscores from all the assets (images/css/js) file names.
Above steps helped me to solve my issue. You can also check this GitHub thread: Asset Packaging error when the solution name has - in the name
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
Hey ganeshsanap
Thanks for you quick response,
As mentioned above I have check all of this and it follows the rules and is sitting at the top of my C drive (Mac os).
And it works when I deploy without --ship, the error only occurs when I add --ship
JaydenMarquardt Then there maybe a space/dash/underscore in the file name of one of the assets. When you deploy with --ship, it includes all client side assets in package.
So, check all the images/css/js/ts/tsx/fonts assets in your solution and remove space/dash/underscore in their names? Did you check this as well?
In one of our solutions there was spaces in image file names which was causing this issue.
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
- Hey @ganeshanap
Thankyou you have solved the issue, there was a single image with a space in it.