Parse

Corona Marketplace Corona Community Plugins
#61

Hi,

I’m getting an error when I try to login to parse using twitter account auth data. The registration phase went OK, but the plug-in seems to have an issue with the callback during a subsequent login attempt. This is the code used:

 parse.request( parse.User.login ) :options( params ) :response(cb)

Where params contain the twitter auth data. I get an error:

ERROR: Runtime error

16:40:37.353  ?:0: attempt to concatenate a table value

16:40:37.353  stack traceback:

16:40:37.353   ?: in function ‘response’

16:40:37.353   C:\Dev\Mobile\Projects\Dare\src\parseInteg.lua:109: in function ‘userLoginImp’

16:40:37.353   C:\Dev\Mobile\Projects\Dare\src\parseInteg.lua:123: in function ‘userLoginWithTwitter’

If I remove the response line (the last line from the code above), than the error does not show, but I have no way of processing the response. Also the debug info is not writing anything when this line is removed, so I can’t really know if a response was ever received.

If I use a regular register (mail+pass) than all goes well using the same code. Both registration and subsequent logins are going as expected. Perhaps there is some glitch in the code that processes the response from the server when it contains some nested tables?

Appreciate your help.

Regards,

Adi

#62

Hi,

Parse is currently unsupported so I’m not sure how much I can help. I don’t have a Parse instance running.

What happens if you do this:

local req = parse.request( parse.User.login )

req:options( params )

req:response( cb )

#63

Hi, It returns the same error.

Parse stand alone is here to stay. Probably will become the most common small scale remote DB solution now that its open. What alternatives will you use for server side?

Is the plug-in pure Lua or based on enterprise?

#64

To clarify, the Corona Parse module is not being supported. Its available in the repo (I think) for anyone to hack on.

My priority is Corona Cloud. And remember that the Lua cloud code is a major aspect of Coronium/Corona Cloud. You won’t get this is Parse open source, nor is there any UI/front-end (last I checked).

We had discussed taking in Parse server, but it limits our abilities to grow the Corona Cloud feature-set over the future.

#65

Hi Chris,

We’ve been using the Parse Plugin plugin for a while, and after the news of Parse shutting down, we’ve migrated to Parse Server hosted on Digital Ocean. However, we can’t seem to get any queries to run, we keep getting:
 

{"error":"Invalid paramater for query: include=sponsor,sub\_categories,sub\_categories.sponsor","code":102}

To be specific, this error does not occur when I don’t pass “options” in the call. Even when doing a simple user sign in such as the one in the following example:
 

parse.request(parse.User.login) :options({username="Chris", password="1234abcd"}) :response(cb)

The call fails with error 200, missing username. So it seems like the options aren’t being passed or encoded correctly. I think it’s also important to note that this error does not occur when using mod_parse.

So to get things straight, are you saying the Parse Plugin will no longer be supported hence it will not work with Parse Server? Or is this just a bug?

Best,
Shehab

#66

Hey guys, does anyone have any input on this yet?

#67

Parse is shutting down, so we need more plug-in which should be used to transfer parse to any other back-end,

#68

Hi David,
 

The Parse Plugin itself is only an interface with your Parse or Parse Server app. It has nothing to do with migrating any existing apps you might have.

However, we (Appduction) have addressed the possible scenarios for migrating from Parse to Parse Server in this blog post. In addition, we have also created this script, which migrates your existing Parse app to a Parse Server with Dashboard on DigitalOcean.

Can anyone in the Corona staff give us an update on the status of the Parse Plugin though? If we’re doing anything wrong from our side, we’d like to know, and if it’s a bug, then an estimate of when it can be addressed would highly be appreciated. We don’t want to revert to mod_parse only to revert back a bit later.

Best,

Shehab

#69

Hi Shehab, 

Do you think this script will work on other ubunto installations? we are usually working with openshift and I know they have a cartridge for parse but unfortunately we weren’t able to make it work. I thought maybe using your script we can make it work. I have zero know how in unix & scripting.

#70

Hi Rune,

Unfortunately, the script is written for Ubuntu 14.04. It might work on other Ubuntu versions with tweaking. But major changes would be required to get it to run on a completetly different Linux distribution.

#71

I have the exactly same problem with login (code: 200, error: username is required) with parse.User.login. 

My code: 

 appData.parse.request( appData.parse.User.login )

  :options( { username=“Chris”, password=“1234abcd” } )

  :response(cb)

Any hint, anyone, please?

#72

Hi,

I am getting an error when using Parse login() function

parse.request( parse.User.login )

  :options( { email = ‘ashraf@shokry.net’, password = ‘aa’ } )

  :response(cb)

the error is always (username/email is required)

I am using back4app backend

Thank you