-
Notifications
You must be signed in to change notification settings - Fork 730
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
Setting Image.Source to local image (added as "Content" to Assets/ folder in UWP project) leads to WASM app never going past the Splashscreen #1
Comments
Ok, figured out what the problem is: If you add an image to UWP's Assets folder (or to any other location within the solution), and point image control's Source property to that image, an app would never complete loading. |
If you put the image in the UWP asset folder (in the UWP Head project), it won't be available for other heads. Is it possible for you to fork the repo and share a commit reproducing the problem? (or any other way to give us more information to reproduce it) I would love to fix the problem for you :-). (by the way, congrats, you're the first one to report a bug on this repo!) |
Hi Carl!
Thanks for reaching out.
I don’t know where I shall put the image for it to be reachable (and visible in UI) within the WASM app. If you can recommend me the step-by-step approach here it would solve the problem.
By now, the only way I can show an image is by linking to an image hosted externally on the web.
What I want is to add an image to the project, ship it with the project, and show it in the UI.
Best Regards,
Daniel
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
…________________________________
From: Carl de Billy <notifications@github.com>
Sent: Tuesday, May 8, 2018 3:17:33 AM
To: nventive/Uno
Cc: Daniel Kornev; State change
Subject: Re: [nventive/Uno] Setting Image.Source to local image (added as "Content" to Assets/ folder in UWP project) leads to WASM app never going past the Splashscreen (#1)
If you put the image in the UWP asset folder (in the UWP Head project), it won't be available for other heads.
Is it possible for you to fork the repo and share a commit reproducing the problem? (or any other way to give us more information to reproduce it) I would love to fix the problem for you :-).
(by the way, congrats, you're the first one to report a bug on this repo!)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFBSq9N1GLMO3-9QmQF9mVtqpEt5ytAgks5twOQdgaJpZM4T1q_1>.
|
@danielkornev "local" files should be available in the wasm app if the build action is set to Thanks for trying uno out ! |
They are available, indeed, but if I set Image.Source to such local file, app never finishes loading in web browsers.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Jérôme Laban <notifications@github.com>
Sent: Tuesday, May 8, 2018 7:10:35 PM
To: nventive/Uno
Cc: Daniel Kornev; Mention
Subject: Re: [nventive/Uno] Setting Image.Source to local image (added as "Content" to Assets/ folder in UWP project) leads to WASM app never going past the Splashscreen (#1)
@danielkornev<https://github.com/danielkornev> "local" files should be available in the wasm app if the build action is set to Content. It seems that for now, wasm does not support this properly, we'll fix it.
Thanks for trying uno out !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFBSq8GIg774ZV-54K3UjhGBnLtYdhILks5twcN7gaJpZM4T1q_1>.
|
Also make sure to use the <Image Source="ms-appx:///Assets/image.png" /> |
I can confirm that any reference to an image causes an error to be thrown during the load of that image. I tried both 'Source="/Assets/ImageName.png"' and 'Source="ms-appx:///Assets/ImageName.png"'. Both versions work in a UWP app; Neither work in wasm. The first few lines of the error from the console:
|
@MarkStega indeed, seems like a minor path parsing issue. Should be easy to fix :) Hang on for the source to be published. |
I updated my nugget packages and it doesn't work for me on wasm (uwp yes). |
@BeaumerF The package that fixed this was not published, you can try updating again, it should work better now. |
@jeromelaban It still doesn't work on my project, the local images let the app on the splash screen (I updated, cleaned and built) |
Update BindableTypeProvidersGenerationTask.cs
test: Add unit tests for UnsetValue returning converter
Related-to: #1 Signed-off-by: Matheus Castello <matheus@castello.eng.br>
* feat: created sample * feat: Use MauiResizetizer dll * chore: added Resizetizer code * chore: moved the solution to another folder * chore: fixed package versions * chore: added targets as Solution Items
OS: Windows 10, 1709, x64
Machine: ThinkPad X1 Carbon 4th Gen, 16GB RAM, Intel Core i7 6th gen (6600), 0.5TB SSD
Visual Studio: 2017 Pro, v 15.6.7
Python 2.7.x installed
The text was updated successfully, but these errors were encountered: