Parse::UserCannotBeAlteredWithoutSessionError

[adelevie]

Parse::UserCannotBeAlteredWithoutSessionError

[adelevie]

Can you post the code that triggers the error?

[ddavtian]

@adelevie sure, seems like it's pointing to the save.

/var/deploy/trivial-mailer/web_head/shared/bundle/ruby/1.9.1/gems/parse-ruby-client- 0.1.15/lib/parse/client.rb:106:in `request'
/var/deploy/trivial-mailer/web_head/shared/bundle/ruby/1.9.1/gems/parse-ruby-client-0.1.15/lib/parse/object.rb:120:in `save'
/var/deploy/trivial-mailer/web_head/releases/20130908003949/app/workers/games_manager.rb:181:in `process_end_games'

In my code, 181 is the following user save.

      # award the win and loss
      winningPlayer["wins"] = Parse::Increment.new(1)
      winningPlayer["centsPaidFor"] += 3
      winningPlayer.save <-- line 181

[ddavtian]

@adelevie README says the following, so I am not sure if I am passing the master-key correctly?

If you want to access your data ignoring all ACLs, you can use the master key provided on the Dashboard.
Instead of the X-Parse-REST-API-Key header, set the X-Parse-Master-Key header. For backward compatibility,
you can also do master-level authentication using HTTP Basic Auth, passing the application id as the username
and the master key as the password. For security, the master key should not be distributed to end users, but if
you are running code in a trusted environment, feel free to use the master key for authentication.

[ddavtian]

Any help on this guys? Many Thanks.

[ddavtian]

I have been digging more on this, what's strange now is that in DEVELOPMENT mode it works, no errors are thrown, but in PRODUCTION mode under RAILS it fails with the above message, any thoughts? In both cases I am using the same exact master_key .. this is confusing.

[adelevie]

Are you able to log any of the outgoing HTTP requests to Parse?

On Thu, Sep 12, 2013 at 6:28 PM, ddavtian [email protected] wrote:

I have been digging more on this, what's strange now is that in
DEVELOPMENT mode it works, no errors are thrown, but in PRODUCTION mode
under RAILS in fails with the above message, any thoughts? In both cases I
am using the same exact master_key .. this is confusing.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/106#issuecomment-24360913
.

[ddavtian]

This was an operator error on my part. I am using resque-scheduler and Parse.init had to be called from within a local method vs. before I had it declared inside the class.

def self.perform(method)
  self.new.send(method)
end

def start()

  Parse.init :application_id => "APP_ID_GOES_HERE",
             :master_key     => "MASTER_KEY_GOES_HERE"