Difference Setting ACL js(parse.com) and android(hosted). #1390

Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

• You've met the prerequisites.
• You're running the latest version of Parse Server.
• You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Description

When I creating new user, I setting acl control. JS(from Parse.com api) side is okay, but Android side (from azure server side) is strange.

• use parse.com for testing somtime.

Environment Setup

• Microsoft Azure
  • Parse Server 2.2.6 (Webapp)
    • Azure Storage File Adapter
    • Forked 'parse-server-example', Customized.
  • MongoDB 3.0.10 (MS Azure VM - Cent OS 6.7)
• Android Build Version 6.0.1, 5.1.x (with Android Studio)
• Google Chrome Browser (49.0.2623.110 (64-bit))
• Mac OS X El Capitain

Steps to reproduce

• Android side

.....  
ParseACL acl = new ParseACL();
acl.setPublicReadAccess(false);
acl.setPublicWriteAccess(false);
user.setACL(acl);
user.signUp();

.....  

• JS Side (from parse.com)

....
var acl = new Parse.ACL();
acl.setPublicReadAccess(false);
acl.setPublicWriteAccess(false);
user.setACL(acl);
user.save(); // or user.signUp();
....

Result :

• Android
  acl column, master key only
• JS (from parse.com)
  acl column, { user_object_id }

Expected :

• same results. / parse.com or stand-alone

Logs/Trace

• none

Please tell me what I missing. Thanks.