• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
User auth not working
#21
(07-05-2019, 12:45 AM)simon.schvartzman Wrote:
(07-04-2019, 10:38 PM)mark_talluto Wrote:
(07-04-2019, 01:30 AM)simon.schvartzman Wrote: Hi, many thanks for the update. Still having problems to get it working...

After restarting LCM here is my situation:

1- the pre-crash records were not restored in cdbUsers
2- I was able to create new users
3- When I start my App I get :
   (2019-07-03 22:14:43.593): Completed apiKey portion of auth
4- When I try to create a new record I get :
   (2019-07-03 22:19:28.413): Error: Failed API Key Authentication
   (2019-07-03 22:19:28.414): Could not create record in cloud.

Is there something else I have to do besides restoring LCM?

p.s.: more than 24 hours out of service for me

The main thing to do is to make sure you have all the updates to LCM. You get this by restarting the app while connected to the internet. It will auto download your updates and install them. There is a log file in the folder structure that will allow you to see your update process. In the log, you will find details about updates that are needed and the status of the updates.  The Mac path is:  /Applications/LiveCloudManager.app/Contents/Resources/_MacOS/spicekit/log.txt
The Windows path will not have the first few folders that are in the Mac path.

Let us know what you find out in there.

Hi Mark, thanks for your reply, please find below the log for today

2019-07-04 09:38:38.012: ########## STARTER RUNNING...
2019-07-04 09:38:38.014: Showing splash...
2019-07-04 09:38:38.324: Splash shown.
2019-07-04 09:38:38.325: Build number: 508.3
2019-07-04 09:38:38.325: Build date: Mon, 20 Feb 2017 16:49:10 -0800
2019-07-04 09:38:38.326: Build engine: 9.0.5-rc-1
2019-07-04 09:38:38.326: Current OS: MacOS 10.14.5
2019-07-04 09:38:38.341: Engine Location: /Applications/LiveCloudManager.app/Contents/MacOS/LiveCloudManager
2019-07-04 09:38:38.345: >>> Resetting the proxy to none by default
2019-07-04 09:38:38.345: Running sk_CheckInternetStatus...
2019-07-04 09:38:39.181: First internet check PASSED after: 834ms
2019-07-04 09:38:39.183: Second internet check PASSED after: 836ms
2019-07-04 09:38:39.597: Third internet check SKIPPED with: out of range
2019-07-04 09:38:39.597: INTERNET STATUS: true
2019-07-04 09:38:39.599: Fetching the SERVER INDEX FILE...
2019-07-04 09:38:39.733: The download of the SERVER INDEX FILE was SUCCESSFUL.
2019-07-04 09:38:39.734: Processing the ON-DISK INDEX FILE.
2019-07-04 09:38:39.749: Local index was NOT MODIFIED.
2019-07-04 09:38:39.751: Update status for this execution: TRUE
2019-07-04 09:38:39.752: Starter complete, switching to PREUPDATER...



2019-07-04 09:38:39.793: ########## PRE UPDATER RUNNING...
2019-07-04 09:38:39.810: Build number: 310.24
2019-07-04 09:38:39.823: Build date: Thu, 25 Feb 2016 09:41:06 -0800
2019-07-04 09:38:39.862: INTERNET STATUS: true
2019-07-04 09:38:39.882: Loading Spicekit LIBRARY...
2019-07-04 09:38:40.067: Registration complete, switching to UPDATER...



2019-07-04 09:38:40.083: ########## UPDATER RUNNING...
2019-07-04 09:38:40.084: Build number: 310.13
2019-07-04 09:38:40.084: Build date: Fri, 12 Feb 2016 16:45:22 -0800
2019-07-04 09:38:40.084: INTERNET STATUS: true
2019-07-04 09:38:40.093: Total updates REQUIRED: 0
2019-07-04 09:38:40.094: Update process COMPLETE.
2019-07-04 09:38:40.228: Submitting system information...
2019-07-04 09:38:40.229: Critical system information is missing or corrupt.
2019-07-04 09:38:40.230: Launching LiveCloudManager...

Please let me know what else can I do

You log file looks good. Based on your email to me, your new project is working as expected. Looks like blue skies ahead.
  Reply
#22
(07-05-2019, 04:46 PM)mark_talluto Wrote:
(07-05-2019, 12:45 AM)simon.schvartzman Wrote:
(07-04-2019, 10:38 PM)mark_talluto Wrote:
(07-04-2019, 01:30 AM)simon.schvartzman Wrote: Hi, many thanks for the update. Still having problems to get it working...

After restarting LCM here is my situation:

1- the pre-crash records were not restored in cdbUsers
2- I was able to create new users
3- When I start my App I get :
   (2019-07-03 22:14:43.593): Completed apiKey portion of auth
4- When I try to create a new record I get :
   (2019-07-03 22:19:28.413): Error: Failed API Key Authentication
   (2019-07-03 22:19:28.414): Could not create record in cloud.

Is there something else I have to do besides restoring LCM?

p.s.: more than 24 hours out of service for me

The main thing to do is to make sure you have all the updates to LCM. You get this by restarting the app while connected to the internet. It will auto download your updates and install them. There is a log file in the folder structure that will allow you to see your update process. In the log, you will find details about updates that are needed and the status of the updates.  The Mac path is:  /Applications/LiveCloudManager.app/Contents/Resources/_MacOS/spicekit/log.txt
The Windows path will not have the first few folders that are in the Mac path.

Let us know what you find out in there.

Hi Mark, thanks for your reply, please find below the log for today

2019-07-04 09:38:38.012: ########## STARTER RUNNING...
2019-07-04 09:38:38.014: Showing splash...
2019-07-04 09:38:38.324: Splash shown.
2019-07-04 09:38:38.325: Build number: 508.3
2019-07-04 09:38:38.325: Build date: Mon, 20 Feb 2017 16:49:10 -0800
2019-07-04 09:38:38.326: Build engine: 9.0.5-rc-1
2019-07-04 09:38:38.326: Current OS: MacOS 10.14.5
2019-07-04 09:38:38.341: Engine Location: /Applications/LiveCloudManager.app/Contents/MacOS/LiveCloudManager
2019-07-04 09:38:38.345: >>> Resetting the proxy to none by default
2019-07-04 09:38:38.345: Running sk_CheckInternetStatus...
2019-07-04 09:38:39.181: First internet check PASSED after: 834ms
2019-07-04 09:38:39.183: Second internet check PASSED after: 836ms
2019-07-04 09:38:39.597: Third internet check SKIPPED with: out of range
2019-07-04 09:38:39.597: INTERNET STATUS: true
2019-07-04 09:38:39.599: Fetching the SERVER INDEX FILE...
2019-07-04 09:38:39.733: The download of the SERVER INDEX FILE was SUCCESSFUL.
2019-07-04 09:38:39.734: Processing the ON-DISK INDEX FILE.
2019-07-04 09:38:39.749: Local index was NOT MODIFIED.
2019-07-04 09:38:39.751: Update status for this execution: TRUE
2019-07-04 09:38:39.752: Starter complete, switching to PREUPDATER...



2019-07-04 09:38:39.793: ########## PRE UPDATER RUNNING...
2019-07-04 09:38:39.810: Build number: 310.24
2019-07-04 09:38:39.823: Build date: Thu, 25 Feb 2016 09:41:06 -0800
2019-07-04 09:38:39.862: INTERNET STATUS: true
2019-07-04 09:38:39.882: Loading Spicekit LIBRARY...
2019-07-04 09:38:40.067: Registration complete, switching to UPDATER...



2019-07-04 09:38:40.083: ########## UPDATER RUNNING...
2019-07-04 09:38:40.084: Build number: 310.13
2019-07-04 09:38:40.084: Build date: Fri, 12 Feb 2016 16:45:22 -0800
2019-07-04 09:38:40.084: INTERNET STATUS: true
2019-07-04 09:38:40.093: Total updates REQUIRED: 0
2019-07-04 09:38:40.094: Update process COMPLETE.
2019-07-04 09:38:40.228: Submitting system information...
2019-07-04 09:38:40.229: Critical system information is missing or corrupt.
2019-07-04 09:38:40.230: Launching LiveCloudManager...

Please let me know what else can I do

You log file looks good. Based on your email to me, your new project is working as expected. Looks like blue skies ahead.
Nope, nothing has changed to me...still no joy, waiting for Efrain to get into my machine
To ";" or not to ";" that is the question
  Reply
#23
Yep, I am still having the same problem too, after restarting LCM. Looking at log file, it looks the same. Note the "Critical system information is missing or corrupt." in the log. Important?

Very frustrating. I set aside this long weekend to teach myself how to use LiveCloud. Can't even get through the most basic part of the tutorial.
  Reply
#24
I have been working on this today. I think the problem is that your apps need to load your tables. Try a cdb_loadTable "*" after doing a user auth. You should be good to go.
  Reply
#25
We used to load your tables for you in the initializeCanelaDB code. You could add cdb_loadTable "*" at the end of your initializeCanelaDB. This will load all of your tables for you. Should you get to the point that you want to manage when your tables are loaded, please take that line out and load your tables as you need them. Have a great weekend.
  Reply
#26
I get :
(2019-07-07 08:39:50.463): Error: Failed API Key Authentication
(2019-07-07 08:39:50.463): Could not read record from cloud.
after calling cdb_read.
everything is fine up to that call. For some reason that is when I get the failed API Key Authorization error.
I have run this forwards, backwards, and every which way that I can. and it always fails at this point.
I even did a sync to local with no errors. apparently not records were sync'ed to the local data.
I now pass the ball back to you guys.
  Reply
#27
Tried the suggestion for modifying the cdb_loadTable. I assume you mean this:

on preOpenStack
initializeCanelaDB
get cdb_auth("test@test.com","password","user")
cdb_loadTable"*"
end preOpenStack

If that is what you were suggesting, it does not seem to do the trick. Restarted the app, but still getting the "Error: Failed API Key Authentication".
  Reply
#28
If you are still having problems, we would like to have a look at a project that is failing for you. Please ZIP up your project including, all stacks of your project and your CanelaDB folder. You can delete your 'database' folder inside of your CanelaDB folder to make the ZIP smaller. We will create a temporary user on your project to help see your problem. If you want us to try a particular user, we will need to have the email and password for that user.

Send your project to: support@canelasoftware.com with the subject: users

Thank you.
  Reply
#29
Update on user auth. Clarence and I worked on this issue last night. He was able to show me code that revealed the problem. We have identified where user auth is failing. We are working to correct the problem. We will post another update once we fix this issue.

For the time being, please authenticate with your developer credentials. This will allow you to continue working on your projects.

We are sorry for the inconvenience this bug has caused. I think we are very close to resolving it.
  Reply
#30
I can confirm that the problem seems to have been corrected.
My limited test shows that this now works!
Thanks!
  Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)