Hi, I (try to) use the NY region but today, after downloading the new version, I no longer can authenticate LCM as can be seen on the attached screen capture.

Waiting for the sun to rise in CA to get an answer from the Livecloud team but meanwhile interested in learn if any one else is experiencing the same...

   

Regards

The following code works OK in iOS (returns "Cloud authentication passed") but never gets to the "answer" line when running on Android (6.0)

on mouseUp
   initializeCanelaDB
   wait 1 seconds -- give some time to become stable
   if cdb_checkInternetStatus() is true then
      put cdb_auth("myemail","mypassword","user") into aux
      answer cdb_result("response")
   end if
end mouseUp
Help please!

Hi everyone,

Just a quick heads up, I'm going to update the server-side libraries for all the regions. The Accounts and Users servers will be down for about 5 minutes. I will begin the process at 1:15 PST. This will be followed by an update to LCM sometime today.

These updates will allow developers to customize the emails sent to users. These emails include the verification email for new users, the forgot password email, and the temporary password email. We will host custom html email files for you on ours servers. You will be able to upload html files through LCM. Developers will also be able to specify a landing page for the verification email and the forgot password email. You will be able to choose your preference, "custom" or "default", for emails and landing pages. These settings will be managed through LCM.

As always, you will be able to see more details about these updates in the LCM change log once you receive the update. Happy coding!

I would like to return the value  in the cdbDateCreated metadata (e.g., "Sun, Oct. 27, 2019 4:06:00 PM").  I know that it is a subkey. How would I do this?

Thanks!

The documentation for LiveCloud has been updated. You can identify which API documentation has changed or has been added in this update by the date located below the API header of each page.

To see the changes, visit the LiveCloud Documentation.

Documentation Update At a Glance:
-Auth
-AuthStatus
-BatchCreate
-BatchDelete
-BatchMerge
-BatchUpdate
-ClearTempBlobs
-Create
-Delete
-ExportAsJSON
-ExportAsLSON
-ProjectDetail
-ProjectID
-ProjectInfo
-Schemaless
-SetUploadMethod
-TableID
-Update
-UserTableName

I've been using arrays and Datagrid tables for some time now, and figured it would be awesome to use Livecloud as a database for obvious reasons.

But I am experiencing issues with the Datagrid not formatting it's height properly. I have several objects on every row and a height of 70. But when setting the dgData of a datagrid to a Livecloud array it sets the height to default.

It seems that the very long id's like 0e0e3c72-24d0-4801-88ba-a3718e1c3fbe are somehow causing this issue. Because when I replace these id's with numbers (1,2,3...) and then set the dgData of the datagrid all is fine with the formatting. 

However this causes some coding headaches regarding editing fields and updating in the Datagrid etc as I have to keep track of ID's.

Anyone else working with Livecloud arrays and datagrids? I've just started but thought I would seek some advice right away.

Your last update to the LCM was massive, and I thank you and the Team for all of the work.
I almost hate to ask the next question though. - Is there a time frame for an update to the docs for the API's and the code snippets?
These documents are very important to all users.

Hello folks,

This update was inspired by a couple of our LiveCloud users. Credit has been applied by the appropriate note. Thanks for the great feedback!
The rest of the changes were derived from our NurseNotes service. The biggest changes are to auth, offline support, and upload of transactions. As always, we hope you find these improvements useful to your apps. Have a great weekend!

######## VERSION 2.3.8 (2019/11/15)
News: IMPORTANT CHANGES! While not required, it is highly suggested that you export the Toolkit to take advantage of these improvements.
- - - - - - - - - -

Added: cdb_authStatus() API for verifying auth status. The data returned is an array like gCSIauthA["target"]["cloud"]["true or false"] and ["local"]["true or false"]. A string of 'False' indicates that no authentication has taken place.
Added: cdb_setUploadMethod 'async' or 'sync' command. The default method is 'sync' if no method has been set. You can control which form to use for cloud calls. In general, you will get better performance from 'async' calls. But, we can not guarantee the order of data being sent with 'async' because the individual transactions are sent very close to each other. When data is sent using 'sync' the APIs will wait for confirmation that the transaction was received before proceeding with the next transaction.
Added: You can now delay Create, Update, Delete, and Merge transactions from being processed. Pass pInternalA["delaySend"] in any of CUDM calls to delay their processing. All delayed transactions are stored in cdbCache. This is a useful way to keep your app offline for performance reasons. Use cdb_flushCache to process the delayed transactions at a time that makes the most sense for your apps.
Added: You can right-click your project and copy your projectID to your clipboard.

Improved: cdbi_tableID can take a single table name, comma delimited list of table names, and an '*'. Single table name returns a string tableID, multiple table names, and '*' return a string list of tableName, tableID. The returned data is an array instead of a string.
Improved: Downloading data will error out immediately if the client is offline. Before, we were trying for the life of the timeout value.
Improved: cdb_flushCache no longer tries three times flush the cache when things go wrong.
Improved: When doing cloud transactions, the locally cached data will no longer automatically flush. We decided to give this control to the developer. To flush your cache, pass cdb_flushCache. Side note: if a Create, Update, Delete, or Merge to cloud is processed, then the cache will be flushed to maintain the order of transactions based on cdbDateCreated value.
Improved: cdb_loadTable will no longer delete clusters that can not be opened. This will be useful for dealing with clients that forget their password. The previous behavior would delete data that could not be decrypted.
Improved: cdb_sync has been optimized to restructure the incoming data to match the client's cluster size.
Improved: csi_loadTable with no params passed uses a more accurate method to determine which tables are not in memory yet and loads them.
Improved: When loading tables, if the cluster size does not match the intended cluster size, we longer delete the clusters.
Improved: cdb_SDK no longer loads all the tables for you.
Improved: When using cdb_auth, the email is now case-sensitive. This falls in line with the fact that we hash the passwords, therefore, making case-sensitivity matter.
Improved: Error reporting from cdb_loadTable
Improved: cdb_auth now does local as well as cloud authentication. You can check your current authentication with the new cdb_authStatus() API.
Improved: All API calls that could modify/delete data will use the authentication status to determine if the action should be allowed.
Improved: All cached cloud calls will get updated authentication credentials at the time the data is flushed to ensure the cloud will receive the data.
Improved: cdbCache is exempt from authentication because it needs to write data before authentication usually takes place.
Improved: Offline mode is determined almost instantaneously, giving your apps a more performant feel.
Improved: cdb_exportAsJSON can take a parameter that contains a full path where you want the data to be written. All tables are now consolidated into single files for easier processing. (Credit to WhenInSpace)
Improved: Many internal APIs have been updated to work with the updated authentication improvements.
Improved: Many internal error messages have been updated to enhance the robustness of all calls.

Bugfix: Fixed an issue where cloning a project could fail. (Credit to Clarence Martin)

A feature Request.
Can you add a feature to set where the exported file gets saved?
Right now, it just saves the exported file to the desktop.
It would be nice if we had an opportunity to save the file to a specific folder.

I have an application that locks up- sometimes for a minute or two and other times to the point of crashing the application altogether.

The only error that I can trap is a tsnet error (6). 
I can only track this in the runtime mode and only using the message box.
there are other messages but they are overridden by the above error.
Is there a way to trap these errors and save them for analysis? 
I do admit that I hit a button to refresh my data often to create this problem but this is a typical uses case for some applications.
Sometimes the error occurs just after the application may is idle for a bit before requesting an update.

is there a way to change the tsnet parameters to let tsnet catch up?
we might want to do a TEAMS session so that you can witness this for yourself.