1. DK BATRA
  2. PowerBuilder
  3. Sunday, 24 December 2017 03:37 AM UTC

Hi all,

While publishing my app on google play, It was rejected with the message appended below.

I found a similar problem reported a month ago and was resolved by a workaround from Appeon team. Kindly help me also with the same as I need to publish the app ASAP.

Thanks

DK Batra

Meesage received from Google Play 

We rejected WAYOUT GST, with package name com.wayout.gst, for violating our Malicious Behavior or User Data policy. If you submitted an update, the previous version of your app is still available on Google Play.

This app uses software that contains security vulnerabilities for users or allows the collection of user data without proper disclosure.

Below is the list of issues and the corresponding APK versions that were detected in your recent submission. Please upgrade your app(s) as soon as possible and increment the version number of the upgraded APK.

Vulnerability APK Version(s) Deadline to fix
OpenSSL

The vulnerabilities were addressed in OpenSSL 1.02f/1.01r. To confirm your OpenSSL version, you can do a grep search for:

\$ unzip -p YourApp.apk | strings | grep "OpenSSL"

You can find more information and next steps in this Google Help Center article.

 

 

1 07/13/2016
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Thursday, 28 December 2017 02:03 AM UTC
  2. PowerBuilder
  3. # 1

Hi DK Batra,

 

I have been working on your case. I sent you an email with an answer to your problem. For these type of issues please open a support ticket to get a better and faster answer.

 

Marco is right. The next release will have this OpenSSL versions added.

 

 

Regards,

Comment
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Sunday, 24 December 2017 10:40 AM UTC
  2. PowerBuilder
  3. # 2

Hello,

that is a known issue

https://community.appeon.com/index.php/qna/q-a/error-publishing-a-custom-appeon-workspace-to-google-play

Hopefully it will be fixed in R2 that is about to be released.

Cheers,

Marco

Comment
  1. DK BATRA
  2. Sunday, 24 December 2017 15:13 PM UTC
Thanks for responding.



I also know that this issue has been reported earlier and was fixed also.



I also request you to provide me the same solution till it is fixed in R2. I need to publish the app at the earliest.



Thanks.



DKB



 



 

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.