Yes it does seem that the Simulator is working with the 'original file' and not the file that should be included in the app.
So once again explained, I have a file A on in my Mac users/frank/documents folder. I include that to Copy Files and compile it into an app. In the app I show a filelist of specialfolder(engine
) and it does show me file A. Then I execute the line like user interactbook
shows in the first posting here, and copy it to specialfolder(documents
) file B. I see the file B appearing live on my Mac in folder Application Support / Simulators / [iOS version ] / Applications / [myapp] / Documents
. It's not an alias. I can connect to file B (a sqlite dbase) and dump the records in an app field. I'm also filelisting the specialfolder(document) and indeed it lists me file B. This all seems correct
Now I keep the app in the Simulator running and then I change the name of the original file A on my mac, which wás included with Copy Files to the app and shóuld be in specialfolder(engine). I turn back to the running app and click again on my button, which does interactbook's line and then connect to my dbase which now is in specialfolder(documents). In the Application Support / Simulator / [version] / Application / [myapp] / Documents
I do see that the file is still there but
is suddenly zero bytes in size, and therefor I get a revdberr..
This kind of prooves to me, that the Simulator shows me the file in the specialfolders right, but it's actually using the original file on my mac and not
the one that supposed to be included in my app
I'm sure this is just Simulator doing this. Or maybe dementia is kicking in early for me? My provisiong profile is outdated at the moment so I can't check on my devices. Please do these steps for yourself and report your findings here..
With regards, Frank