Amplify-android: Developer Menu can't be disabled in Debug Mode

Created on 4 Sep 2020  路  17Comments  路  Source: aws-amplify/amplify-android

When integrating '_com.amplifyframework:aws-auth-cognito:1.3.1_' I have noticed that a Developer Menu Screen has been introduced when the application is in Debug mode. It appears if the device is shaken.

However, the developer Menu is enabled by default and cannot be disabled, also the shake detector is way too sensitive
https://github.com/aws-amplify/amplify-android/blob/f345bda690eec84d5e83fecb4efba7e50bcf8c11/core/src/main/java/com/amplifyframework/core/Amplify.java#L145

Developer Tools Feature Request

Most helpful comment

Hi @mihirap,

You should be able to disable the debug menu in 1.3.2 and above by passing a custom AmplifyConfiguration to Amplify.configure() like this:

val config = AmplifyConfiguration.builder(applicationContext)
    .devMenuEnabled(false)
    .build()
Amplify.configure(config)

All 17 comments

I am also facing the same issue. I don't really want my app to show the DeveloperMenu to the users...

I am also facing the same issues. Anyway to disable this
image

Howdy! That will only show up in debug mode. We'll circle back next week on an option to disable and tweaks to the shake sensitivity.

@estiukamobi Android application generating two app shortcuts with same icon and name. One is opening app were another open menu like KayIlory's Issue
In my case it is not disable in release mode too.
Please help @jamesonwilliams

Heya @24Lathiya -- are you seeing this behavior with our 1.3.1 release?

@jpignata OMG this issue gone with 1.3.1 thanks.

I think we should discuss two items:

1) Do we have an option to disable this functionality in debug?
2) Should we tweak the sensitivity?

Here is the ReactNative ShakeDetector implementation, that is used for showing the ReactNative debug menu. Copying the sensitivity values would probably make sense. The comments indicate they only trigger on detecting a "rage shake". 馃槀

This is still in 1.3.1... And bad form adding without a disable flag, it's super annoying.

@kwatkins Got it. We'll make a fix right away for the next release to reduce the sensitivity and add a flag to disable.

821 went out in the 1.3.2 release.

1.3.1, 1.3.2, 1.4.1 I checked with these versions. But can't disable it.

Hi @mihirap,

You should be able to disable the debug menu in 1.3.2 and above by passing a custom AmplifyConfiguration to Amplify.configure() like this:

val config = AmplifyConfiguration.builder(applicationContext)
    .devMenuEnabled(false)
    .build()
Amplify.configure(config)

Hi @mihirap,

You should be able to disable the debug menu in 1.3.2 and above by passing a custom AmplifyConfiguration to Amplify.configure() like this:

val config = AmplifyConfiguration.builder(applicationContext)
    .devMenuEnabled(false)
    .build()
Amplify.configure(config)

It works. Thanks.

Hi @richardmcclellan I'm facing same issue in my flutter application. Is there any solution for that?

Hi @richardmcclellan I'm facing same issue in my flutter application. Is there any solution for that?

We should just disable the dev menu entirely in Flutter right now. https://github.com/aws-amplify/amplify-flutter/pull/266

The feature can be added to Flutter in a more controlled manner. There will need to be some supporting work in the Dart layer.

Was this page helpful?
0 / 5 - 0 ratings