Android Studio Errors

Discussion in 'Technical Discussion' started by Xoctrebla, Jun 20, 2018.

  1. Xoctrebla

    Xoctrebla Avid Boxer

    Joined:
    Mar 19, 2017
    Messages:
    143
    Likes Received:
    77
    Android Studio Errors

    I originally had 6 errors, resolved 1 (multidex) of them and now have 5 and am stuck. I was hoping others have come across these error and can share there solutions.

    I followed the tutorials and they’re pretty straight forward. My first thought is buildbox is saving my Android settings as Apple setting because the settings don’t seem to be saving https://screencast.com/t/RKxTK8yeYWTd . However someone mentioned that Android Setting should still be saved. That being said any help being pointed in the right direction in solving the following errors would greatly be appreciated.

    I have API Android 8.0 Oreo installed along with the SDK Tools: Android Sdk Build-Tools, Emulator SDK Platform-Tool, Sdk Tools and both Repositories along with the Intel x86.

    Solution to Multidex: https://stackoverflow.com/questions/40309249/getting-multidex-error-even-after-setting-min-sdk-21

    Failed to resolve: multidex *FIXED
    Failed to resolve: play-services-ads
    Failed to resolve: play-services-auth
    Failed to resolve: firebase-auth-license
    Failed to resolve: runtime
    Failed to resolve: common
     

    Attached Files:

  2. DariusGuerrero

    DariusGuerrero Avid Boxer Staff Member

    Joined:
    Dec 22, 2016
    Messages:
    431
    Likes Received:
    326
  3. Andy

    Andy Miniboss Boxer

    Joined:
    Sep 24, 2015
    Messages:
    2,152
    Likes Received:
    1,545
    Seems like this is looking more and more like a local issue with the gradle cache. On a Mac, you can just delete the cache directory ($HOME/.gradle/caches/) directory. I'm not sure if the equivalent is exactly the same on Windows but it should be similar.
     
  4. Xoctrebla

    Xoctrebla Avid Boxer

    Joined:
    Mar 19, 2017
    Messages:
    143
    Likes Received:
    77
    @DariusGuerrero you Da Man!
    This totally fixed all the Errors and now I just have to figure out...

    Your app has an apk with version code 1 that requests the following permission(s): android.permission.READ_PHONE_STATE. Apps using these permissions in an APK are required to have a privacy policy set.
     
  5. jcalle

    jcalle Miniboss Boxer

    Joined:
    Sep 25, 2015
    Messages:
    1,104
    Likes Received:
    475
    It is a very old subject.
    I advise you to remove the permission if you do not use it.
    You have to create a Privacy Policy.
    https://www.buildbox.com/forum/index.php?threads/solved-privacy-policy-warning-from-google.8432/
    http://buildbox.com/forum/index.php?threads/privacy-policy-link-for-google-play.9077/#post-48742

    These are my recommendations for permissions:
    android.permission.INTERNET to access: Play Games, advertising,(required if you use google play and ADS)
    com.android.vending.BILLING to make purchases within the app (NO required if you not use purchases in APP)
    android.permission.ACCESS_NETWORK_STATE to check internet (recommended)
    android.permission.ACCESS_WIFI_STATE to check access to internet for Wifi (recommended)
    android.permission.ACCESS_COARSE_LOCATION to display ads based on their country (NO required, NO recommended)
    android.permission.WRITE_EXTERNAL_STORAGE to write APP in ExternalSD (required if you install APP in ExternalSD)
    android.permission.READ_PHONE_STATE to read IMEI and telephone number (NO required, NO recommended)
     
    Maylock likes this.
  6. Xoctrebla

    Xoctrebla Avid Boxer

    Joined:
    Mar 19, 2017
    Messages:
    143
    Likes Received:
    77
    Thx @jcalle I removed the permission...
    This can be done by opening manifest file, looking for "<uses-permission android:name="android.permission.READ_PHONE_STATE" />
     
    Maylock likes this.

Share This Page