Play Store Deep Links problem

[Raphael Awoseyin]

Play Store console complains of an inaccessible "Deep Link" in my app. Apparently, something in the app points to http://ds

I didn't think a DS link would be embedded in my app. But, how do I fix this?

[Alan Hendry]

HI,

If no-one gets this problem,

then I presume it's something in your code

What version of DS and the builder are you using?

Regards, ah

[Raphael Awoseyin]

Attached is a screenshot of the message from Play Store console,

[Raphael Awoseyin]

Yet another Play Store console error.

What are all these errors popping up? It is my first attempt at getting my app into the Play Store and I can't figure out why I should be getting these errors that seem to relate to DS.

[John Praise]

I'm also experiencing the same set of errors. Deep link & unsafe cipher mode

[Symbroson]

What kind of app are you trying to publish? Is it a python or node.js app or some other special app type? Are you using extra modules or anything else besides native DS controls or plugins?

About the usafe cipher error: Are you using the Crypt component maybe or something similar?

[John Praise]

For me, I'm building an HTML app. With the default code obfuscation on build

Crypt component wasn't used at all 

[Dave]

Hi Guys,

You can ignore all these issues, it won't stop your app being published.  These 'errors' are actually only advisory and should really be called 'warnings' in my opinion.

Google has recently started doing a lot of scanning of APKs and flagging issues that are not always relevant.  

If you are not using the DS Crypt component then the warning about Ciphers is not relevant to you... even if you have, then you probably don't need to worry unless you are processing financial or other sensitive data.

The deep link issue is because we use the ds:// scheme to do single sign on in DS, but the Google Play APK scanners do not understand this.  We will probably remove this from the generated manifest in a later release.  You could manually remove it if your really want by using a 3rd party manifest editor, but its easier to just ignore it for now.

Regards

David

[Dave]

To clarify - 

Even if you are not using the Crypt object, it is still part of the DS library in all APKs built by DS, so Google detects it even if u are not using it. 

You can still publish, don't worry. DroidScript is published with these same errors. It's not really an error, just a warning. 

We can't just simply upgrade it to a newer cypher because previous users might not be able to decrypt their data. We will probably move it into a plugin in future versions and or work out some way of detecting which cypher has been used to encrypt the existing data (if thats possible).