Rollo62

What about libVLC, PasLibVlc ?

@pyscripter Sometimes Im wondering what made Python so popular in the first place. Now I know, it was PyScripter IDE

Not quite sure what you're doing right now, changing your code or TMS code, or what. But the TDictinary is maybe worth to replace by Spring4D dictionary, to circumvent such errors..

@wva Now re-installed all that, but still no luck. XCode doesn't recognize my device. The command shows which should be OK I guess. I think that I did this on Windows VM, so I'm not sure how this was before re-install. Sorry, too many VM's running, and too late in the evening Anyway, I did the complete clean install. If you have still some tips what to change in the .vmx file, would be great. Otherwise I have to move to real hardware now, as VM debug is broken.

@wva Thanks for the hints. Indeed this command doesn't show the "usbarbritator". But that is missing also in earlier VM's, which is still working perfectly fine with my USB devices. Anyway, I will try to re-install the VmWare. What I don't get is your note "... download the full installer ...". When I make a normal update, via the check for updates, do I get a different installer then ? I've never had seen any difference there.

Bold is Old. Not sure if this matches the newest trends in ORM, we'll see.

@Dave Nottage Sorry, I've tried do read as carefully as possible, I'm working on other issues too. I have seen the libSystem, not /system, you'right the /system folder is missing here too. While I can see the /system in iPhoneOS.sdk 13.5 latest. From this post, it seems to be stubs for iOS, and the real libCache is needed for Macos only. That Macos folder is still there in my SDK: Maybe not a good idea to use the Macos folder instead, the question would be who needs and links to libCache. Clarifications: 1. From your blog 2. From your last post before

@Dave Nottage Yes, I've took that picture from Finder, in the post above. It exists in the iPhoneOS.sdk path, as well as in the iPhoneOS13.6.sdk path. Also I did a normal update via AppStore, to get that picture incl. /System. But maybe in case of somethings wrong, I considered a full clean, I did some times before. Was not necessary this time.

@pyscripter Maybe you could clarify what that "Python" note really means ? It sounds as if Python projects would be planned to be full citizen in the IDE one day ? Now it should already be possible to support "Python scripts" in the editor of the IDE, with an LSP support.

@Dave Nottage Maybe this is a hint

Strange, I think I did the same here in my VM. But as you know I have other issues, VM cannot find my devices anymore, only a real Mac on XCode 11.6 can still do. I assume you did already XCode cleanup complete and reinstall. Edit: Something like this or that.

So could you fix it ? I just made a normal XCode update to SDK13.6, did you do this update via command line ? Have you checked if XCode is veryfied ? Like that, or

@Dave Nottage Regarding the iOS13.6 SDK, with XCode 11.6, I'm not sure what is missing there. I just checked the XCode package content, looks like this, seems OK to me at first sight The /System folder is not "empty", but I have not checked out the SDK in my projects yet.

It might have. When I tested .pas extensions, this might occur into strange temporary .$$$ files, when I try to debug and edit. Not sure why that happened, but I moved back to .inc then. Compiling and running should be fine, I am talking about the development process of such file, when opening it from the caller unit.

No problem seen yet, what Platform are you talking about ?

Hi there, related to this post, but I think its a very different issue. As explained, I used XCode 11.5.x and iOS13.5 for quite a while (weeks and months) happily, and then focused a little more on Android, leaving aside iOS, not connecting to XCode during this time. Then after maybe 2-3 weeks later, I've got back to my (unchanged) iOS / XCode / OS setup, and suddenly XCode didn't recognize my phone anymore. I'm using the following setup, and did the following measures to get back on track, but nothing helped so far. Working in host (Macos 10.15.4), current VmWare Fusion (11.5.6) on a current MacBook with enough power and space I didn't change anything, it was running well before when plug in the phone, the USB selection dialog appears, and I can connect to the VM, as usual VmWare shows that iPhone connected to the VM-image, just as it should and as before VM image can show the USB, when also iPhone entry is visible, just as it should The problem is that XCode doesn't recognize the iPhone at all But I can build release packages normally. I've tried rebooting Host, Client VM, iPhone many times I've tried updating all to latest XCode 11.6 and iOS 13.6 I've changes the SIM-Card, to be sure there is no strange hardware error. I've un-trusted the iPhone, but still XCode doesn't react at all This seems not to be an easy one this time, and I'm not sure if this is related to iOS13.6 at all, because this did stop working at iOS13.5 already. Maybe somebody has a clue what could go wrong here ?

I have to give up for the moment, this already costs too much time. The certificates are OK, and I've tried to repair, revoke, renew them several times. The result stays the same: I cannot see my devices in VmWare Fusion - XCode anymore, but on real hardware - XCode it works as usual. For the moment I have to work on hardware Macos again, until I find more time to look into this. This is not an Delphi issue at all, since I'm not even able to do anything in XCode.

Oh, yes. It seems to be another certificate issue: In the Certificates/Devices section I've got this message Then had to confirm: Confirm again: and again ... until you've made yourself really clear that you want to move on development, and not suddenly want to stop it. What is that good for, another level of bu**hit to punish us developers, I never noticed that before ? Maybe this came from the complete change of AppleConnect last year. Anyway, that bad news is that afterwards XCode STILL did not see my devices, although I restartet it already. But I have a reasonable clue now, and try to peek here and there further ... Why dont they give a clear message in XCode then, as Apple knows very well whats going on.

Yes, there are NO devices. Exactly that is the problem. It seems that the phone in the OS is not really distributed to XCode anymore, while I can see that at VM scope and in the Macos guest scope system info. I used an USB2.0 hub to connect it to the USB3.0 ports of the host, that worked well for years, maybe something has changed now. In the VM I have set USB2.0 compatibility. I'm going to check today if it makes a difference if I connect it to the USB3.0 port directy. BTW: When I connect the phone to the host Macos XCode (an older version), then the same phone on the same USB2.0 hub is detected and listed in the Devices & Simulators, as usual. Edit: When I try with an older iPhone 6, also this connects well to the VM, but is not visible for XCode.

I would love to use that even more often, but I'm very careful with this function too. From my experiece this is not very reliable if you use more than one file of same name, which you want to use as default. That depends on the search path which one is taken. The documentation here says that it take the Search library path definitions, I hope that true that its also searches them in the right order. If you change the search path order, then you might see strange errors in that case above. Of course it should be ..\ on Windows, thats what I use there always.

I can agree to that, since I use interposer heavily. Some years ago I have heard that some people have the philosophy to wrap everything into interposers. I'm not going that far yet, but close. I can understand well to have a "safety" layer between the framework and your app. That serves a lot of useful purposes: to easily manage bugfixes at a centralized place for each component to make workarounds around some conceptual limitations of some components to enhance the components with new, custom features they don't interfear with normal designer process, so no need to install custom components That are enough reasons for me to consider interposers everywhere 🙂

Ok, after along way back and forth to the Patch 3, it seems to work more or less. Patch 1 and Patch 2 worked directly, but Patch 3 needed some extra care somehow. I had to re-create .dproj's and re-order units, before it runs without issues. Not sure what the real reasons are, but now all my projects run unter 10.3.3 to 10.4 P1 P2 P3. Whats still open to me is the TChart issue, I hope it gets done soon. https://quality.embarcadero.com/browse/RSP-29414 https://quality.embarcadero.com/browse/RSP-29694 https://quality.embarcadero.com/browse/RSP-28780 https://quality.embarcadero.com/browse/RSP-29414 So I have to disable my chart in the projects. I also faces issues with the Grijjy cloud logger, so I have to turn this off and move to somthing different, but thats acceptable. All in all debugging feels quite sluggish, but compiling and running seems to work then finally. The LSP runs better, so I really hope I'm ready now for Update 1, and I don't need to waste more time in porting stuff.

Try to delete the existing app on the phone, before uploading the new one.

Nope: An update to Macos 10.15.6 doesn't solve it. So maybe I'm foreced to update XCode and/or iOS too, but I try to keep it at the moment, maybe there is another idea howto make XCode detecting my phone again. Updating iOS to 13.6 will also break my XCode connection, and I cannot debug SDK 13.5 there.

Maybe somewhat related to this, I just fell (again) into the other Apple trap. By leaving aside the working XCode VM, only for some days/weeks, to test and prepare Android. Today I try moving back to the current system (same VM, same XCode, sam OS 10.15.5, same iPhone (13.5), etc. The iPhone is suddenly no more detected by XCode, even that iPhone is connected to the VM and listed in the USB. (usualy restart, reboot OS and Phone already done). I had similar cases before, where current, working setups ( of the former versions ), suddenly disappear to function with XCode and RadStudio. And yes, IT IS NOT A DELPHI ISSUE. The general recommendation to this is, to update to the latest versions (at least thats what Apple says ). If I do that, then I'm back to entry 1. of this thread, and the new versions cause other issues. So at the moment I try to install the new OS 10.15.6 only, with the hope that this might be sufficient to detect iPhone again. This is typical Apple, to me it looks like a modern way of planned obsolescense, which is absolutely annoying. I only can say, if I wouldn't have to provide iOS solutions, I would recommend to everybody to stay away from Apple purchases. Usually I'm quite neutral, but Apple already costs me days of my lifetime, for their daily nonsenses. Go and better buy Android products