APK is marked as debuggable??

IanVinkIanVink CAInsider, University ✭✭✭
edited May 2017 in Xamarin.Android

Visual Studio 2017

I have Archived a Release Xamarin Forms app and I am attempting to publish it with the Archive Manager. The app builds, is Archived and is signed, but after upload Google Play responds with "APK is marked as debuggable".

I see no Debug symbol and this app was uploaded last month without any setting changed in between versions.

Ideas?

Best Answer

Answers

  • IanVinkIanVink CAInsider, University ✭✭✭
    edited May 2017

    in /obj/Release/android/AndroidManifest.xml, the debug is set to true?? My .csproj has no <debugsymbols> so how is it generated if I don't setthat?

       <application android:label="Credential" android:hardwareAccelerated="true" **android:debuggable="true"**
    
  • IanVinkIanVink CAInsider, University ✭✭✭

    My .csProj has Release set to no debug either:

    <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
      <DebugSymbols>false</DebugSymbols>
     <DebugType>none</DebugType>
     <Optimize>true</Optimize>
     <OutputPath>bin\Release\</OutputPath>
     <DefineConstants>
     </DefineConstants>
     <ErrorReport>prompt</ErrorReport>
     <WarningLevel>4</WarningLevel>
     <AndroidUseSharedRuntime>False</AndroidUseSharedRuntime>
    </PropertyGroup>
    
  • LjusnanLjusnan DEMember ✭✭✭

    Look at this: https://developer.xamarin.com/guides/android/advanced_topics/debuggable_attribute/
    Check your AndroidManifest and your MainApplication.cs, if you have.

  • IanVinkIanVink CAInsider, University ✭✭✭

    It's a bug in the newest Visual Studio 2017 code.

    Here's the update: https://bugzilla.xamarin.com/show_bug.cgi?id=56075

  • AndrewEblingAndrewEbling USMember

    Did you guys find a resolution for this issue? I'm struggling with the same problem.

  • IanVinkIanVink CAInsider, University ✭✭✭

    seems to have "gone away" with new versions

  • IanVinkIanVink CAInsider, University ✭✭✭
    Accepted Answer

    Newer versions of VS2017 fixed the issue.

  • Mani787Mani787 INMember ✭✭✭

    I have changed the debug mode to release mode in configuration manager of vs2017. After that, i rebuild the my application. And then i tried the samething. It has been resolved my problem and i dont the same issue anymore.

Sign In or Register to comment.