AndroidManifest.xml - Debuggable=false

[softwaretirol]

Description

I have declared a service within our AndroidManifest.xml

<service
        android:name="com.stripe.stripeterminal.TapToPayService"
        android:process=":stripetaptopay"
        android:exported="true"
        android:isolatedProcess="true"
        android:debuggable="false"/>

On building our app we are getting a generated AndroidManifest.xml

<provider android:name="mono.MonoRuntimeProvider_1" android:exported="false" android:initOrder="1999999998" android:process=":stripetaptopay" android:authorities="com.my.app.mono.MonoRuntimeProvider_1.__mono_init__" />

And the "debuggable"=false is gone, therefore during debugging it is trying to attach a debugger on the second process, but that wont work because the debug port is already used by the app process itself.
Can we somehow transfer the debuggable=false to the generated manifest?

Thanks!

Steps to Reproduce

No response

Link to public reproduction project repository

No response

Version with bug

9.0.110 SR11

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

No response

Affected platforms

Android

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

09-17 15:52:50.541 W/monodroid-debug( 1085): Trying to initialize the debugger with options: --debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8847,server=y,embedding=1,timeout=30000
09-17 15:52:50.541 W/monodroid-debug( 1085): Accepted stdout connection: -1
09-17 15:52:50.541 F/monodroid-debug( 1085): Error accepting stdout and stderr (127.0.0.1:8848): Address already in use

[jonathanpeppers]

Can you share the full contents of the generated manifest? And which value is unexpected?

[jonpryor]

@softwaretirol: your description confuses me, as "debuggable" is an <application/> attribute: https://developer.android.com/guide/topics/manifest/application-element#debug

The <provider/> element does not document a debuggable attribute: https://developer.android.com/guide/topics/manifest/provider-element

Likewise, <service/> does not document a "debuggable" attribute: https://developer.android.com/guide/topics/manifest/service-element

(Yes, you added one, but I believe it will be ignored.)

You're also comparing <service/> to <provider/>; these are not the same.

Finally, platforms/android-36/data/res/values/attrs_manifest.xml has a debuggable attribute in:

    <declare-styleable name="AndroidManifestApplication" parent="AndroidManifest">
        <attr name="debuggable" />
    </declare-styleable>

and that's the only location that uses debuggable.

---

If you want your app to be debuggable, you need to set the <application/> debuggable attribute. You can do this in code by using ApplicationAttribute:

[assembly: Application(Debuggable=true)]

Or, if you have an Application subclass:

[Application(Debuggable=true)]
partial class MyApp : Android.App.Application {
}

[dotnet-policy-service]

Hi @@softwaretirol. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.