ToddFrankson

Me to. I still have his Delphi tips from D3 or so......I still reference every now and again.

12.1-12.3

Sometimes, I have to go back in and re-select my images.

Click "Run" from the menu bar. Click "Parameters" In the Parameters field type in "-cleaninstall" Repeat for each platform

Should it exist in the Cache-Dir-.... Directory too?

BTW- Where locally does Delphi Store the /System/Library/PrivateFrameworks/DocumentManager.framework/DocumentManager path and the Other linker paths?

Yup. I get it still on a few projects I haven't messed with in a few months. It seems that if I change the SDK (IOS Simulator) back and forth a few times, from 18.4 to 18.5, it goes away in some cases.

So I get this on any pre existing App for IOS Simulator (iphone16 IOS 18.4) [DCC Error] E2597 ld: warning: directory not found for option '-LComponent' [DCC Fatal Error] F2588 Linker error code: 3221225477 ($c0000005) And this for any new blank project I try to run on the simulator ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(intercept_dispatch.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(objc_dispatch.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(rtti_raw_invoke_arm64.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(thunk_blocks.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(objc_blocks.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(thunk_helpers.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(so_init.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(delphi_support.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(cxa_support_c.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: warning: object file (c:\program files (x86)\embarcadero\studio\23.0\lib\iOSSimARM64\Release\librtlhelper.a(debug_support.o)) was built for newer iOS Simulator version (14.0) than being linked (11.0) ld: file not found: /System/Library/PrivateFrameworks/DocumentManager.framework/DocumentManager for architecture arm64 [DCC Fatal Error] F2588 Linker error code: 1 ($00000001) Nothing else I cleared the Cache-dir-... on the Mac and on my local machine. Now I can deploy new blank projects to IOS Simulator, but the first project still gives the same error...

Uninstalled the patch, reinstalled the patch. I can now get IOS apps working..... IOS simulator still gives me an error though I'll get the message tomorrow.

PAServer 14.3.14.5,, Xcode 16.4(16F6), IOS 18.5 SDK, IOS 18.5

Even a blank new Multi-Platform Project? Splash screen shows, then app closes

My apps were set at 11. After the latest IOS Update, not a single one will open. I was trying to see if they would run with the minimum OS set higher. I also believe that for Apple Store submission, the minimum needs to be set higher than 13.

So, May patch.... Tried to compile an IOS app that already ran fine. The only change was setting it to run on IOS 15.0 minimum... Syntax check fine. Go to run it on the phone, error count goes up and up like @Dave Nottage reported. Anyone know why? I am down currently for anything IOS

Dunno what it is, when I have an issue, I post, and 2 hours later the issue goes away.