Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-20103] Remote images aren't loading on Android 6

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionDuplicate
Resolution Date2015-12-10T08:39:18.000+0000
Affected Version/sRelease 5.1.0, Release 5.1.1
Fix Version/sn/a
ComponentsAndroid
Labelsandroid
ReporterEduard Florea
AssigneeAshraf Abu
Created2015-12-04T18:20:46.000+0000
Updated2017-03-22T22:23:19.000+0000

Description

My team is working on a social app which uses a lot of remote images. After we upgraded to Titanium SDK 5.1.1 GA and change the android:targetSdkVersion to 23 we ran into an issue when none of the remote images are loading. This is a very big issue from our understanding, since all of the devices with Android 6 will not show any remote images. In the screenshot attached, you can see a simple app which is basically a window with an ImageView. The ImageView is using a random remote image. The image loads on Android 5, but on Android 6 it doesn't.

Attachments

FileDateSize
Android6_vs_Android5_Remote_image.png2015-12-04T18:17:30.000+0000148451

Comments

  1. Ashraf Abu 2015-12-08

  2. Ashraf Abu 2015-12-08

    Alternatively, as you mentioned, setting the Android SDK to version 22, will force it to use the old Permissions system even on Android 6.0. This will grant the permissions automatically on run time. To do this, you need to use an Titanium SDK 5_0_X version. I recommend 5.0.3. via 
     appc ti sdk install --branch 5_0_X
    . You can then add these lines to your manifest in TiApp.xml:- 
           <android xmlns:android="http://schemas.android.com/apk/res/android">
           <manifest>
               <uses-sdk android:targetSdkVersion="22"/>
           </manifest>
       </android>
    This will allow remote images to load as the permissions are granted via the old permission system.
  3. Eduard Florea 2015-12-10

    Thanks guys! Requesting camera permissions fixed the issue!
  4. Rainer Schleevoigt 2016-02-05

    Maybe this module helps: https://github.com/gimdongwoo/Ti-Android-RequestStoragePermission
  5. Rainer Schleevoigt 2016-02-05

    I tried to send a downgraded version 23=>22 This is the error message from playstore: "This configuration can not be published for the following reasons: It is forbidden for devices that were originally using M-permissions (for SDK 23 and above) to perform a downgrade to APKs, the old-style permissions to use (for SDK 22 and lower). This comes with a change of version 42 (for SDK 23) prior to version 43 (for SDK 22)."
  6. Ashraf Abu 2016-02-10

    Just an update. There is a fix in TIMOB-20251 that solves the issue of remote images. There shouldn't be any permissions required.
  7. Fokke Zandbergen 2016-02-18

    [~bimmel] this or TIMOB-19899 (same issue) should be in the 5.2.0 release notes as well.
  8. Fokke Zandbergen 2016-02-18

    [~bimmel] never mind, TIMOB-20251 is mentioned, although I find this ticket's title clearer since it's the actual bug people experienced.
  9. Lee Morris 2017-03-22

    Closing ticket as duplicate and links to the related ticket have been provided above.

JSON Source