I have trouble running empty FMX application on iOS simulator. Application shows splash screen and dies.
I have trouble running empty FMX application on iOS simulator. Application shows splash screen and dies.
I am not using VM, but network connection between macOS and Windows.
Any ideas?
Tokyo 10.2.3 + PAServer 10.2.1.13
Windows 10 April Update
macOS High Sierra 10.13.5
iOS 11.2 SDK
Xcode 9.2
I am not using VM, but network connection between macOS and Windows.
Any ideas?
Tokyo 10.2.3 + PAServer 10.2.1.13
Windows 10 April Update
macOS High Sierra 10.13.5
iOS 11.2 SDK
Xcode 9.2
Mh.. i think 11.2 (Simulator) is not supported. It's mentioned somewhere in the docs IIRC. Try it with a 10.x Simulator
ReplyDeleteTried with 9.3 but it didn't work... I'll try with 10.x
ReplyDeleteDon't think it has changed in the meantime but it is mentioned here that Simulator 11 is not supported until Mac OSX 64bit support is added:
ReplyDeletecommunity.embarcadero.com - Build iOS 11 ready apps with RAD Studio 10.2.1
Another option may be that you aren't importing everything you should. Have a look at that too.
ReplyDeleteAndrea Raimondi for a blank application?
ReplyDeleteActually... yes. The iPhone target is peculiar and on Berlin I am 99% certain that you have to include a bunch of things that may not be included outright.
ReplyDeleteIt is - as far as I can tell - either rather silly or confusing (in which case I haven't understood properly how this works).
Andrea Raimondi if that is true then it is not silly OR confusing, it is both ;)
ReplyDeleteNo luck with 10.2 simulator either...
ReplyDeleteMichael Thuma It shows splash and closes, so it is not waiting problem... at least not from my side.
ReplyDeleteDalija Prasnikar I think my suggestion could at least help. You'd better google to make sure which bits are essential :)
ReplyDeleteI am trying to debug some ARC code... I can use iOS device - but debugger starts only once in a blue moon there. Anyway I could also use Android device, but going through ARM assembler is a nightmare.
ReplyDeleteI used to debug on Simulator through VM, but after all the recent CPU security updates VM runs so slow it is unusable.
And I cannot use Linux VM - because I am debugging FireMonkey.
This is why we need Windows ARC compiler.
https://wiert.me/2018/06/07/one-more-reason-to-have-an-arc-win32-compiler-tracking-down-memory-leaks-efficiently/
Hi Dalija Prasnikar - I get this a lot, usually after updating X Code®.
ReplyDeleteThe latest update actually uninstalled the version of the framework I was using (I sometimes get suspicious about the intention of those updates). In the past, it was so bad, I started running OS X®, X Code®, and PA Server in a VM to test the updates with before updating the physical machines.
Anyway, for a blank app, you should not need to deploy any additional files.
I do not have my notes for dealing with handy, so off the top of my (old) head:
I find that sometimes, updating the sdk files may help (and I am unsure of why, noting that usually, some file conflict is often reported).
Debugging in iOS® simulator can be rough. Be sure to look at PA Server's window for clues.
Often, I find that running without debugging gets past the initial start-up crash that sounds exactly like you are reporting (meaning you may have to initially resort to other means of debugging - not fun).
Simulator has a option to "wipe it back to clean" (I forget the exact name of the option) that can sometimes be helpful. I wish that it did not auto start when I choose to do that. Anyway, my best guess is that something does not get updated properly with "project1" (or whatever name may get re-used). Try changing the project name!
I will be updating a dev VM shortly, and will undoubtedly run into this issue "YA" (yet again). When I do, I will try to remember to copy out my notes on getting around this and send them to you.
I wish I could be more helpful (today).
Joe C. Hecht Thanks for the tips... I already tried most of them... but you never know they might help someone else.
ReplyDeleteWhen I could not run my test application, I focused on running anything even without debugging.
It is probably due to some configuration + Xcode issue. I never tried to run under Simulator with this setup. So it was not something that worked and then stopped,. I tried all the "fast" solutions... none of them worked.
Life is too short... so I have given up for the time being....
Dalija Prasnikar good luck! Know that you are not alone on this one.
ReplyDeleteJoe C. Hecht It would be much better situation if I would be the only one having this issues ;)
ReplyDeleteMichael Thuma It never worked with this setup between two physical computers. It worked when I ran Delphi under VM in OSX and it was on different Mac, not the one I am currently connecting to.
ReplyDeleteDalija Prasnikar
ReplyDeleteI had a similar issue when i attempted to do a quick test after applying the iOS Patch.
I recently updated all software on my iMac to the latest XCode, macOS.
I removed the older Delphi simulator and created V11.4, i selected the iphone 7 (iOS 10.3) and the simulator works.
The MacOS test tells me about the 32 bit problem which is fine for now.
The iPhones all work as well.
Richard Baroniunas Thanks, I will try that... I am just not sure when...
ReplyDeleteDalija Prasnikar Good luck. I found that FMX is a pain especially that Apple keeps updating which makes it difficult for any company to keep up.
ReplyDeleteDalija Prasnikar this is what you need
ReplyDeleteXcode > Preferences > components > ios simulator 10.3.1
Xcode > preferences > locations > command line tool > Xcode 9.3.1 (9e501)
I am assuming that the rest you have configured (paserver, sdks, profiles, etc)
Nirav Kaku Thanks...
ReplyDeleteReinstalling Xcode (any version) is currently out of the question. When the time comes to do that, I will consider all possible combinations :)
Dalija Prasnikar I did the updates of both Tokyo and X Code this weekend, - I cannot believe it - I had no issues.
ReplyDeleteJoe C. Hecht Nice...
ReplyDeleteMichael Thuma No. I guess Xcode update would be in order and I don't have time do do that... or roll back if it messes things up even more.
ReplyDelete