Skip to content

PFUser become results in 206 in iOS SDK #444

Description

@edualm

Hello,

There appears to be a problem when using PFUser.becomeInBackground(sessionToken) from an iOS app.

All writes to the user object return a "[Error]: cannot modify user (Code: 206, Version: 1.12.0)".

Using the REST API with the session token returned by my Cloud Code works (I attempted to edit a field in the user object, and it worked).

If you are unable to reproduce this issue / need code samples, just say.

Thanks for the attention,
Eduardo Almeida

Activity

  1. alioguzhan commented on Feb 16, 2016

    @alioguzhan
    Contributor

    same here. i get this error when using [user saveInBackgroundWithBlock...] method. And this is the full error:

    error : {
        NSLocalizedDescription = "cannot modify user jV2QyE2Hpy";
        code = 206;
        error = "cannot modify user jV2QyE2Hpy";
        temporary = 0;
    }
    
  2. natanrolnik commented on Feb 16, 2016

    @natanrolnik
    Contributor

    @MegaEduX @aoguzhan You guys may check #430 that was merged recently and may fix this issue. Try running parse-server pointing to Head instead of the latest release, and check if it solves your problem.

  3. edualm commented on Feb 16, 2016

    @edualm
    Author

    @natanrolnik Downloaded latest release from GitHub, built it... The same error still happens.

  4. absolutlabs commented on Feb 17, 2016

    @absolutlabs

    We're facing the same issue with users authenticated through -and only- Facebook : #427 .
    What about you ? Did you get this error with username/password too ?

  5. edualm commented on Feb 17, 2016

    @edualm
    Author

    @absolutlabs: I am using Digits, using an adapted version for parse-server of this code: https://github.com/felix-dumit/PFUser-Digits/blob/master/user.js

    I never tried username/password, as I don't have it setup in my app.

  6. myyellowshoe commented on Feb 18, 2016

    @myyellowshoe

    Having a similar issue with the Javascript SDK and Parse Server on Heroku.

  7. myyellowshoe commented on Feb 18, 2016

    @myyellowshoe

    It looks like mine was related to using Parse.User.current().fetch() in the Javascript SDK.
    Which works, but seems like its messing with the tokens and making me unable to post changes to server.

  8. edualm commented on Feb 18, 2016

    @edualm
    Author

    Could be related.

    Just tested with the latest commit, still not working.

  9. gfosco commented on Feb 26, 2016

    @gfosco
    Contributor

    This may have been fixed... please update to 2.1.3 and if you're still having a problem please open a new issue and provide as much information as possible. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions