Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[Bug] Image Control doesn't work #9900

Closed
yinyue200 opened this issue Mar 9, 2020 · 25 comments
Closed

[Bug] Image Control doesn't work #9900

yinyue200 opened this issue Mar 9, 2020 · 25 comments

Comments

@yinyue200
Copy link

yinyue200 commented Mar 9, 2020

Description

Steps to Reproduce

  1. archive https://github.com/yinyue200/xamarinformstest in release mode
  2. install the apk
  3. go to about page

Expected Behavior

show the image

Actual Behavior

can't show the image

Basic Information

  • Version with issue:
  • Last known good version:4.4
  • IDE:VS2019
  • Platform Target Frameworks:
    • iOS:
    • Android: 10
    • UWP:
  • Android Support Library Version: AndroidX
  • Nuget Packages:
  • Affected Devices:

Screenshots

Screenshot_2020-03-09-22-37-01-264_com companynam

Reproduction Link

https://github.com/yinyue200/xamarinformstest
https://github.com/yinyue200/xamarinformstest/releases/tag/1.0

Workaround

use FFImageLoading

@yinyue200 yinyue200 added s/unverified New report that has yet to be verified t/bug 🐛 labels Mar 9, 2020
@pauldipietro pauldipietro added this to New in Triage Mar 9, 2020
@ouma
Copy link

ouma commented Mar 10, 2020

same here , toolbar icons not showing after archiving in release mode

@rasel-tr
Copy link

+1, I lost images on the Android platform for my Forms project suddenly after upgraded the Xamarin.Forms package.

@StephaneDelcroix StephaneDelcroix moved this from New to Ready For Work in Triage Mar 12, 2020
@StephaneDelcroix
Copy link
Member

does disabling the linker fixes it for you ?

@yinyue200
Copy link
Author

@StephaneDelcroix It failed to archive if linker set to None.
devenv_2020-03-12_22-18-35

@samhouts samhouts moved this from Ready For Work to Needs Estimate in Triage Mar 12, 2020
@ouma
Copy link

ouma commented Mar 13, 2020

does disabling the linker fixes it for you ?

No. The issue still persists

@nhdanh
Copy link

nhdanh commented Mar 17, 2020

Same Error when update to lastest XF

@NamCkiku
Copy link

same here , toolbar icons and image not showing after archiving in release mode

@rasel-tr
Copy link

Any news for this problem? It is a blocker for my project and I can't release a new version.

@rasel-tr
Copy link

Disabling bundle assemblies into native code option resolves my problem.

@hig-dev
Copy link

hig-dev commented Mar 23, 2020

I have the same problem and I can confirm that disabling "bundle assemblies into native code" fixes the problem. However, this is not an option for me for the Release build. The bug is maybe related to #1595

@PaulVrugt
Copy link

We are running into the same problem. Disabling "bundle assemblies into native code" fixes it, but we don't want to do this.

@CNouws
Copy link

CNouws commented Mar 31, 2020

Here the same problem and indeed disabling "bundle assemblies into native code" fixes the problem. But this is not an option. Any update please?

@rasel-tr
Copy link

With newly released version 16.5.2, the problem still continues. It starts with 16.5.0 and this is the second update ignoring this problem :(

@samhouts
Copy link
Member

samhouts commented Apr 6, 2020

It looks like this might be related to xamarin/AndroidX#64 (comment). @mattleibow Can you confirm, please? Thanks!!

@jonpryor
Copy link
Member

jonpryor commented Apr 6, 2020

@hig-dev mentioned:

[disabling "bundle assemblies into native code"] is not an option for me for the Release build

Would you mind elaborating on why setting $(BundleAssemblies)=False isn't an option? We are strongly considering removing support for $(BundleAssemblies) in .NET 5, and would like to better understand why people are using it. (It's not a very good obfuscation technology, and for it not being very good it increases on-device memory usage and slows down app startup times.)

@nexxuno
Copy link

nexxuno commented Apr 9, 2020

Hello, I guess the reason why we are using these kind of bad obfuscation tecniques is that the only other option (dotfuscator) has a starting price of around 4k$ a year so we do what we can with what we have. Any suggestion of better tecnologies for an affordable / free price with azure CI pipelines integrations on microsoft hosted environments?

Anyway this is a bad regression.

@tranb3r
Copy link

tranb3r commented Apr 10, 2020

We would like to better understand why people are using it.

It's decreasing size of apk a lot.

@rasel-tr
Copy link

Also I don't want all the DLLs of the app to be seen in the /lib folder of the apk

@samhouts samhouts added 4.5.0 regression on 4.5.0 external-components and removed s/unverified New report that has yet to be verified labels May 6, 2020
@samhouts samhouts moved this from Needs Estimate to External in Triage May 6, 2020
@ia5634
Copy link

ia5634 commented May 7, 2020

The same problem is here. It occured when I updated Xamarin.Forms from nuget.

Current Xamarin.Forms version is v4.6.0.726. It's definetely related to new versions (I think it began with v4.5). There was no problem while using an old version (cant remember old version number :/)

What I tested;
When "target framework is 10" and "bundle assemblies... = true" => problem
When "target framework is 10" and "bundle assemblies... = false" => not problem

When "target framework is 9" and "bundle assembliies... = true" => not problem
When "target framework is 9" and "bundle assemblies... = false" => not problem

@ia5634
Copy link

ia5634 commented May 12, 2020

An update: There is no problem with Xamarin.Forms v4.4.0.991864 (from NuGet)

"Target framework is 10" and "bundle assemblies... = true" = not problem at all.

@Keivan-Mousavi
Copy link

It's been more 2 months now. This bug cannot be solved???

@tranb3r
Copy link

tranb3r commented May 15, 2020

This is clearly a regression, so it should be simple enough for the xamarin team to fix it.
But sadly they don't seem to care at all about it. And it gives more and more the feeling that they don't care about their own users.

Anyway, it's not even clear to me if this is a Xamarin.Forms or a Xamarin.Android regression ?
And starting from which version ?

@samhouts samhouts added this to the 4.5.0 milestone May 19, 2020
@yankarinRG
Copy link

I am facing the same problem with the latest version of Xamarin.Forms (4.6.0.800) and targetSdkVersion="29" (Android 10 - Queen Cake): if "Bundle assemblies into native code" is enabled, the Image won't show.

@rasel-tr
Copy link

Also there isn't any fix for this in

4.7.0.773-pre1

4.7.0.813-pre2

Pre Release versions. What a regression is it that can not be fixed for more that 2 months.

@PureWeen
Copy link
Contributor

Closing in favor of xamarin/AndroidX#106 as this is not a Forms issue

Triage automation moved this from External to Closed May 25, 2020
@samhouts samhouts removed this from Closed in Triage Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests