This is how it looks like in my Android Studio 3.5 beta2:

 [![enter image description here][1]][1]

You can see that I don&#39;t hide obsolete packages and request package details. Now we see that the old **NDK** package is replaced by the new **NDK (Side by side)**, which allows to keep both NDK r19 and r20.

The reason why they are making the change is that switching to the latest version of NDK is not always painless, and many developers prefer to stay with an older version, at least for some projects.

The bottom line is that it is OK to use the NDK that you have installed, but it will be replaced with the new package some time later when you upgrade the Android Studio.

  [1]: https://i.stack.imgur.com/z5BRy.png

NDK (Side by side) is irrelevant for Android Gradle Plugin earlier than 3.5. However, the components available for download by SDK manager aren&#39;t customizable based on Android Gradle Plugin version so the side by side NDKs will appear.

Starting in 3.5, you can specify a particular version of NDK in your build.gradle by setting, for example:

  android.ndkVersion &#39;19.2.5345600&#39;

The non side by side NDK has been marked as obsolete. Which means it won&#39;t appear in the SDK manager list unless you uncheck Hide obsolete packages --or-- you already have that NDK installed locally. 



According to Android Studio 3.5 release document, it says:
&quot;Android Studio 3.5 allows you to use multiple versions of the Android NDK side-by-side in your build.gradle file. This should allow you to have more reproducible builds and mitigate incompatibilities between NDK versions and the Android gradle plugin.&quot; I think side by side means you may use multiple NDK versions simultaneously. It is a new version to replace the ndk bundle version.


 

This has been surprisingly confusing for me. I thought Docker&#39;s Image ID is its SHA256 hash. However, apparently the result from `docker image ls --digests` (listed under the column header `DIGEST`) is different from the `IMAGE ID` of that image.

For example

```
docker image ls --digests alpine
REPOSITORY          TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
alpine              latest              sha256:769fddc7cc2f0a1c35abb2f91432e8beecf83916c421420e6a6da9f8975464b6   055936d39205        2 weeks ago         5.53MB
```

while 

```
docker image ls --no-trunc
REPOSITORY                                             TAG                 IMAGE ID                                                                  CREATED             SIZE
...
alpine                                                 latest              sha256:055936d3920576da37aa9bc460d70c5f212028bda1c08c0879aedf03d7a66ea1   2 weeks ago         5.53MB
```

Clearly `sha256:055936d3920576da37aa9bc460d70c5f212028bda1c08c0879aedf03d7a66ea1` (IMAGE ID) and `sha256:769fddc7cc2f0a1c35abb2f91432e8beecf83916c421420e6a6da9f8975464b6` (DIGEST) are not the same value. But why? What&#39;s the purpose of having two different `sha256` hashes of the same image. How are they calculated, respectively?

I was confused by this when reading the book *Docker Deep Dive*, and I haven&#39;t been able to find a clear answer either in the book or online.

What&#39;s the difference between a Docker image&#39;s Image ID and its Digest?

Whenever I run my code with requests or do a pip install I get this message 
```
/usr/lib/python2.7/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.2) or chardet (3.0.4) doesn&#39;t match a supported version!
  RequestsDependencyWarning)
```

I have tried upgrading chardet, urllib3 and requests but nothing is working, anyone know how can I fix this?

Edit: https://stackoverflow.com/questions/50202238/requestsdependencywarning-urllib3-1-9-1-or-chardet-2-3-0-doesnt-match-a-su &lt;-- This did not fix my problem.

RequestsDependencyWarning: urllib3 (1.25.2) or chardet (3.0.4) doesn&#39;t match a supported version! Fix

There&#39;s a ndk (side-by-side) at [![the sdk manager][1]][1].
Is it needed to install or just need to install the ndk? 

  [1]: https://i.stack.imgur.com/UO8KE.jpg

Whats NDK (side-by-side) in android sdk?

<p>There's a ndk (side-by-side) at <a href="https://i.stack.imgur.com/UO8KE.jpg" target="_blank" rel="noopener noreferrer"><img src="https://i.stack.imgur.com/UO8KE.jpg" alt="the sdk manager"></a>.
Is it needed to install or just need to install the ndk?</p>


I am trying to run a selected build variant but giving me following error in Run tab,

&gt;Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: No outputs for the main artifact of variant: madhyapradesh-debug

So kindly suggest the solution to it.

How to fix &#39;Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: No outputs for the main artifact of variant:&#39;

As [getExternalStoragePublicDirectory][1] has been deprecated in `Android Q`, and the recommendation is to use other means. then how can we specify that we want to store the generated photos from a camera app into the `DCIM` folder, or a custom sub-folder within the `DCIM`?

The documentation states that the next 3 options are the new preferred alternatives:

 1. [Context#getExternalFilesDir(String)][2]
 2. [MediaStore][3]
 3. [Intent#ACTION_OPEN_DOCUMENT][4]

Option 1 is out of the questions as it would mean that the photos get deleted if the app gets uninstalled.

Option 3 is also not a choice, as it would require the user to pick the location through the SAF file explorer.

We are left with option 2, the MediaStore; but at the time of this question there is no documentation on how to use it as a replacement for getExternalStoragePublicDirectory in Android Q.


  [1]: https://developer.android.com/reference/android/os/Environment#getExternalStoragePublicDirectory(java.lang.String)
  [2]: https://developer.android.com/reference/android/content/Context.html#getExternalFilesDir(java.lang.String)
  [3]: https://developer.android.com/reference/android/provider/MediaStore.html
  [4]: https://developer.android.com/reference/android/content/Intent.html#ACTION_OPEN_DOCUMENT

getExternalStoragePublicDirectory deprecated in Android Q

My application works fine from Android 4.3 until Android 9 Pie, but my application doesn&#39;t work on Android 10 (Q API 29) and crashes. This is my logcat - why this is happening?

    java.lang.RuntimeException: Unable to start activity 
         ComponentInfo{ir.mahdi.circulars/ir.mahdi.circulars.MainActivity}: 
         android.view.InflateException: Binary XML file line #17 
         in ir.mahdi.circulars:layout/abc_screen_simple: Binary XML file line #17 
         in ir.mahdi.circulars:layout/abc_screen_simple: 
             Error inflating class androidx.appcompat.widget.FitWindowsLinearLayout

and this is my mainActivity.xml

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;androidx.coordinatorlayout.widget.CoordinatorLayout xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;
        xmlns:app=&quot;http://schemas.android.com/apk/res-auto&quot;
        xmlns:tools=&quot;http://schemas.android.com/tools&quot;
        android:layout_width=&quot;match_parent&quot;
        android:layout_height=&quot;match_parent&quot;
        android:background=&quot;@color/white&quot;
        android:layoutDirection=&quot;ltr&quot;
        tools:context=&quot;.MainActivity&quot;&gt;
        
      
    &lt;/androidx.coordinatorlayout.widget.CoordinatorLayout&gt;

update

    apply plugin: &#39;com.android.application&#39;
    
    android {
        compileSdkVersion 29
        defaultConfig {
            minSdkVersion 16
            targetSdkVersion 29
            multiDexEnabled true
            testInstrumentationRunner &quot;androidx.test.runner.AndroidJUnitRunner&quot;
        }
        buildTypes {
            release {
                minifyEnabled false
                proguardFiles getDefaultProguardFile(&#39;proguard-android-optimize.txt&#39;), &#39;proguard-rules.pro&#39;
            }
        } }
    
    dependencies {
        implementation fileTree(dir: &#39;libs&#39;, include: [&#39;*.jar&#39;])
        implementation &#39;androidx.appcompat:appcompat:1.0.0&#39;
        implementation &#39;com.google.android.material:material:1.0.0&#39;
        implementation &#39;androidx.constraintlayout:constraintlayout:1.1.3&#39;
        testImplementation &#39;junit:junit:4.12&#39;
        androidTestImplementation &#39;androidx.test:runner:1.2.0&#39;
        androidTestImplementation &#39;androidx.test.espresso:espresso-core:3.2.0&#39; }



Crash on Android 10 (InflateException in layout/abc_screen_simple line #17)

I have integrated Snapchat&#39;s Creative Kit in my Android app. After processing, I receive an image from the server in the form of Byte Array which I am saving to the disk and then sending the file to the Snapchat&#39;s Creative Kit as shown below.

     private fun downloadImage(
        fileName: String,
        imageByteArray: ByteArray?): Uri? {
        val state = Environment.getExternalStorageState()

        if (Environment.MEDIA_MOUNTED == state) {
            val downloadDir = File(
                Environment.getExternalStorageDirectory(), context?.getString(R.string.app_name)
            )

            if (!downloadDir.isDirectory) {
                downloadDir.mkdirs()
            }

            val file = File(downloadDir, fileName)
            var ostream: FileOutputStream? = null
            try {
                ostream = FileOutputStream(file)
                ostream.write(imageByteArray)
                ostream.flush()
                ostream.close()
                }
            } catch (e: IOException) {
                e.printStackTrace()
            }
        
        val snapCreativeKitApi = SnapCreative.getApi(context!!)
        val snapMediaFactory = SnapCreative.getMediaFactory(context!!)
        lateinit var snapPhotoFile: SnapPhotoFile
        try {
            snapPhotoFile = snapMediaFactory.getSnapPhotoFromFile(file)
        } catch (e: SnapMediaSizeException) {
            return
        }
        val snapPhotoContent = SnapPhotoContent(snapPhotoFile)
        snapCreativeKitApi.send(snapPhotoContent)
        }
    }

I have also added `provider` in the manifest file as shown below:

      &lt;provider
            android:name=&quot;androidx.core.content.FileProvider&quot;
            android:authorities=&quot;${applicationId}.provider&quot;
            android:exported=&quot;false&quot;
            android:grantUriPermissions=&quot;true&quot;&gt;
            &lt;meta-data
                android:name=&quot;android.support.FILE_PROVIDER_PATHS&quot;
                android:resource=&quot;@xml/provider_paths_app&quot; /&gt;
        &lt;/provider&gt;

And in the `provider_paths_app.xml`, I have tried all the possible paths by referring [this][1] answer and none of them works.

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;paths xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;&gt;
    &lt;external-path
        name=&quot;My App Name&quot;
        path=&quot;.&quot; /&gt;
    &lt;/paths&gt;


  [1]: https://stackoverflow.com/questions/37953476/android-how-to-get-a-content-uri-for-a-file-in-the-external-storage-public-d

With the above path, I am getting the below error.

    Couldn&#39;t find meta-data for provider with authority my.package.name.fileprovider

All I have to do is send this image to Snapchat but I am unable to figure out what I am doing wrong. Any help will be appreciated.



Couldn&#39;t find meta-data for provider with authority

New Gradle Sync is not supported due to containing Kotlin modules using an unsupported plugin version

After updating Android Studio and Gradle to 3.5,
I now get this error:

&gt;NDK Resolution Outcome: Project settings: Gradle model version=5.4.1, NDK version is UNKNOWN

I changed the Gradle version in build-gradle back to 3.4.2 but it didn&#39;t help.

NDK Resolution Outcome: Project settings: Gradle model version=5.4.1, NDK version is UNKNOWN error

After updating to **Android Gradle plugin** `3.6.0` (released Feb 24, 2020), several project independently started failing with:

    No version of NDK matched the requested version 20.0.5594570. Versions available locally: 21.0.6113669

It&#39;s quite simple to &quot;fix&quot; this locally by installing the older expected ndk version:

    sdkmanager &#39;ndk;20.0.5594570&#39;

However, my question is: Where and how is this older version specified? And how do I update it so it matches the latest version `21.0.6113669`?

No version of NDK matched the requested version

I have updated Android Studio to 4.1 in Macbook but not able to run app after updating. It is giving following error 

    Execution failed for task &#39;:app:stripDebugDebugSymbols&#39;.
    NDK at ~/Library/Android/sdk/ndk-bundle did not have a source.properties file

Content Type	Original Author	Original Content on Stackoverflow
Question	Daniel Mana	View Question on Stackoverflow
Solution 1 - Android	Alex Cohn	View Answer on Stackoverflow
Solution 2 - Android	Jomo Fisher	View Answer on Stackoverflow
Solution 3 - Android	Kenneth Yang	View Answer on Stackoverflow

Whats NDK (side-by-side) in android sdk?

Android Problem Overview

Android Solutions

Solution 1 - Android

Solution 2 - Android

Solution 3 - Android

RequestsDependencyWarning: urllib3 (1.25.2) or chardet (3.0.4) doesn't match a supported version! Fix

What's the difference between a Docker image's Image ID and its Digest?

Attributions