Mac Standalone x IDE different behaviour

[simon.schvartzman]

Hi guys, the following code gives different results running on the IDE versus running standalone

command startLiveCloud
   initializeCanelaDB
   answer "Internet Status:" & cdb_checkInternetStatus()
   get cdb_auth("xxx@xxx.com","xxxx","user")
   answer "Initialization Response: " & cdb_result("response")
   cdb_loadTable ("Users")
   answer "Load Response: " & cdb_result("response")
   answer "Users: " & cdb_count("Users", "cloud")
end startLiveCloud

Internet Status is "true" on both cases
"Initialization Response: " and "Load Response: " are empty on both cases (as they should)
"Users: " returns 16 (which is correct) on the IDE and nothing (empty! not even 0) on the standalone.


Before you ask before building the standalone I have added the full CanelaDB folder to be copied and manually added the 4 needed inclusions. (double checked it many times)

This is driving me crazy!!!!

Any hints?

[efrain.c]

Hi Simon,

I was not able to reproduce your bug. Can you try putting an answer dialog after

answer "Users: " & cdb_count("Users", "cloud")

with

answer "Count: " & cdb_result("response")

to see if cdb_count is causing an issue for you on standalone?

[simon.schvartzman]

Hi Efrain, 

answer "Count: " & cdb_result("response") 

retrieves empty on both environments.

I'm happy to share with you my code (both source and dmg) if needed. 

BTW if you want to try it yourself I'm using the stack of the lesson below in order to generate the dmg..

http://lessons.livecode.com/m/4071/l/112...c-appstore

Regards

[simon.schvartzman]

Hi Efrain, I found out what I was doing wrong.

Instead of installing the App into my Mac I was running it from the virtual drive and that was the problem.

Once I installed it on the physical drive everything worked OK.

Thanks and sorry for the confusion

[mark_talluto]

You should be able to run your app from any drive. I am wondering if there is a path related issue. Did you try this with the updated libraries?

[simon.schvartzman]

Hi Mark, it was my own fault, as you guessed I was doing something wrong with the path to the drive.

Thanks for replying.