-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iTunesArtwork missing #786
Comments
There's an issue with the template where the The workaround is to move the files to the right place. In your example, you should find the files at |
The issue should be resolved with new projects generated using release Due to the |
Thank you everyone very much for the fix.
…On 7/5/2020 9:51 AM, Jonathan Froon wrote:
The issue should be resolved with new projects generated using release
|v1.9.0+|. For an existing project, the steps suggested by
@lukepothier <https://github.com/lukepothier> in moving the files back
to the root directory should resolve the issue.
Due to the |iTunesArtwork| files not having any file extensions
MSBuild was duplicating the path inside the NuGet packaged version
published in the VSIX. Which was why this only affected the VSIX
version of MvxScaffolding and not the |dotnet new| templates.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#786 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRSIMWGR23CSYXSCAZO5ZLR2CHPVANCNFSM4OP4KUSQ>.
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
|
I am on a Mac with VS 2019 doing a compile in debug or release mode but using iPhone; the iPhoneSimulator works OK and i receive the following message:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(3,3): Error: '/Users/MM/Documents/GitHub/MOrtho/src/MOrtho.iOS/iTunesArtwork' not found. (MOrtho.iOS)
I have changed the properties of the iTunesArtwork to always copy. Any idea for this problem?
The text was updated successfully, but these errors were encountered: