Dear team, after this update the LCM is complete inoperative (at least to me):
Please see screen shoot attached
- When I open LCM I see the login screen with jason's email & sometimes the message "The CanelaDB is missing..."
- the password is shown in spite of how the "show password" checkbox is set
- it doesn't recognise my email as a valid user account (neither can't I validate my password nor can reset it)
Note1: I downloaded a fresh new LCM and nothing
Note2: I tried to create a new free account and wasn't able to do so, there was no response from the system regarding why it was not created...
It has been really very frustrating to work with this product, I sincerely hope it starts to do better in the near future. I'm starting to wonder if it was a good move to pay for the full year in advance
p.s.: here goes my weekend when I was expecting to do some progress with my project using LiveCloud
I want to create a list of cdb_Users.
I want to use this list to select a user to update or delete.
I have looked at the user api's and can't find the api that would let me create such a list.
Can I do this via a query and can you give an example script?
Help! I am suddenly unable to update a table, and also can't view the table using LiveCloud Manager.
These are the error messages I am getting for about the last 3 hours. This came on suddenly. System was working before that.
(2019-07-15 11:36:06.171): The server response could not be downloaded at this time.
(2019-07-15 11:36:40.034): The server response could not be downloaded at this time.
(2019-07-15 11:37:10.044): The server response could not be downloaded at this time.
(2019-07-15 11:37:10.044): Error: There was a problem getting a response from the server for cdb_batchCreateCloud request.
(2019-07-15 11:37:10.044): Could not create record in cloud.
Authorization seems to work but nothing beyond that.
(2019-07-15 11:42:55.436): Completed apiKey portion of auth
When I delete a table in the LCM I immediately get a Blob View window. There are no BLOBs and that might be because I don't have nay.
--Just thought that this something that you may want to look into.
Posted by: Pebah - 07-13-2019, 04:06 AM - Forum: Bug Reports
- No Replies
I'm trying to log in to LiveCloud Manager, forgot password, navigated to Recover Password, entered email address, then saw error dialog "Failed to reset password."
Hello. I have some ideas about how what I'm about to ask may work but a quick tip would be helpful. How do I set up more than one app to update the same LiveCloud table?
Simple example situation: I have a LiveCode app I'm using for development and to build my understanding of LiveCloud. But what I ultimately want is to update a suite of existing LiveCode apps so that instead of talking to tables in a MySQL database they'll be talking to analogous tables in LiveCloud, the same tables my dev app talks to. Hope that's possible and guess that it is.
Is it just a matter of putting those LiveCode apps in the same folder as my dev/LiveCloud learning app and putting the same initialization scripts in each LiveCode app? Or is there more to it? Thanks in advance.
What is the correct procedure for updating clients version ?
While I am preparing to lunch our Beta version of MIXKIT, I came across a problem about
how to go when updating clients version after a LiveCloud Updates.
Until now when there’s been and API LiveCloud update, the procedure is to update de API and replace it
in the folder with the new version, and after, update de code in the App.
That works fine in a developper environment but what will happen in an App distributed scenario.
If I am not mistaking, if the LiveCloud Database get an upgrade, all the previous app using the previous version stop working ?
Am I making a bad presumption or is this the case ?
If this is the case how can we support upgrade to our clients when sometimes App distribution on Apple take a couple of days to offer a new version update ?
Will our clients have an App that will stop working, until they receive a new update threw the App Store?
Is presently one way to support LiveCloud Database update to modify our App code to basically do the following ?
Put in the app some code that Ping the LiveCloud server and verify the current version
Then compare it with the client version and if the LiveCloud version is newer…
Execute a code that will download the latest version of the API and installed it on the client hardware.
Execute code copy of the LiveCloud API code that as been save as test only stack code, so they can also be downloaded without
having to download a full new version from the App store.
Run a test to assure that the update report a ping that is working and then run the client login
What scenario do you propose for client App update that are already running in the field so there is no interruption of service to our customers ?
Which part of the example query below (on the docs page for AdvancedQuery) ensures that only "record IDs with first name ending with 'n' or 'y' will be included in the line-delimited list"? If, as it appears to me, that portion of the query is missing, could you please supply the full query? Thanks in advance.
Code:
# We want to find all clients that have last name "Smith"
# and a first name that ends with "n" or "y".
local tDataA, tAdvancedMap, tTable, tTarget, tResultFormat
# first query
put "lastName" into tDataA["lName"]["key"]
put "=" into tDataA["lName"]["operator"]
put "Smith" into tDataA["lName"]["value"]
# advanced map
put "LName" into tAdvancedMap
put "clients" into tTable
put "cloud" into tTarget
put "recordList" into tResultFormat
put cdb_advancedQuery(tDataA,tAdvancedMap,tTable,tTarget,tResultFormat)
Hi LiveCloud users, is it just me or the folks at LiveCloud take too long to answer?
When compared with the Livecode forum this one is much slower and for a product that is in the early stage I guess quick support for the early adopters should be a must after all we could be a reference...
Hello,
I'm testing liveCloud on a LOCAL ONLY database. I delete some records and everything is fine, but after quit and restart the deleted records are still there!
