Post

Replies

Boosts

Views

Activity

Reply to Xcode 26.4: Regressions in Intelligence features
I can already tell you, nothing works for me anymore. I updated to macOS 26.4. This morning, it updated Xcode to 26.4 as well. As a result, I had to reinstall Codex, which I did. I logged in, and now nothing works at all. I can submit a request in the chat, sometimes I get a short response, and then it starts thinking about something and never stops. I think it is amazing what kind of unfinished mess Apple is delivering once again. This is absolutely unbelievable. I am furious that such a broken system is being provided to us developers. It would be the easiest thing for Apple to simply test Codex. If they are not even providing us with the latest Codex versions and instead releasing outdated versions with their Xcode, it is outrageous that we are given something so completely unfinished and nonfunctional. With macOS 26.3 and Xcode 26.3, I was at least able to program perfectly fine with Codex and developed several apps. Now I wake up in the morning, want to continue working on my apps, and great job, Apple, thank you for this massive bug. I cannot develop anything anymore. Codex no longer works with Xcode 26.4. I warn everyone against installing Xcode 26.4. You can assume that Codex will no longer work. At least it does not work for me. There is no way to check why it is not working. Apple blocks the entire reasoning process. We are not shown any logs, we cannot see anything. Nothing is possible. I can even specify a log path in the Codex config file, yet no logs are written there. Once again, I find it incredible how Apple treats us. They simply do not give a damn. The main thing is that Apple gets to preconfigure everything, and we developers have no control over how Codex functions within Xcode. Once again, I say thank you, Apple, for restricting us in every possible way. I am just furious. I do not understand how something this broken can be released. And I am curious how many weeks we will have to wait before Apple finally takes action. Just look at which Codex version is included in the latest Xcode release. We are now on Codex version 1.0.6. Just think about that. An ancient version with no Fast Tier available. But okay, Apple, you must know what you are doing. I am furious, just completely annoyed, and that is all I have to say.
Mar ’26
Reply to Pls fix m1 chip issues with external monitor hidpi
I just get my M1 Max 16" MacBook Pro and are shocked that I see it do not support 3840x2160 HiDPI with my Apple Pro Display XDR 32" !!! I contact Apple for this issue and they told me, the Pro Display XDR are NOT compatible with M1 Chips !!! Absolute outstanding Information I get. But they will fix that, when does nobody known.  Theres another big issue in compatibility with M1 Macs, the 32" Pro Display XDR does only Show "Million Color" instead of "Billion Color". The Internat Display from new 16" MacBook Pro M1 Max does finally shows itself "Billion Colors" but can not show this on external 32" Pro Display XDR. I report Apple for this issue. Unbelievable for me how this hughe bug can be present!! I'm on Monterey 12.0.1 and the issues is already present.
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’21
Reply to Xcode 26.4: Regressions in Intelligence features
I can already tell you, nothing works for me anymore. I updated to macOS 26.4. This morning, it updated Xcode to 26.4 as well. As a result, I had to reinstall Codex, which I did. I logged in, and now nothing works at all. I can submit a request in the chat, sometimes I get a short response, and then it starts thinking about something and never stops. I think it is amazing what kind of unfinished mess Apple is delivering once again. This is absolutely unbelievable. I am furious that such a broken system is being provided to us developers. It would be the easiest thing for Apple to simply test Codex. If they are not even providing us with the latest Codex versions and instead releasing outdated versions with their Xcode, it is outrageous that we are given something so completely unfinished and nonfunctional. With macOS 26.3 and Xcode 26.3, I was at least able to program perfectly fine with Codex and developed several apps. Now I wake up in the morning, want to continue working on my apps, and great job, Apple, thank you for this massive bug. I cannot develop anything anymore. Codex no longer works with Xcode 26.4. I warn everyone against installing Xcode 26.4. You can assume that Codex will no longer work. At least it does not work for me. There is no way to check why it is not working. Apple blocks the entire reasoning process. We are not shown any logs, we cannot see anything. Nothing is possible. I can even specify a log path in the Codex config file, yet no logs are written there. Once again, I find it incredible how Apple treats us. They simply do not give a damn. The main thing is that Apple gets to preconfigure everything, and we developers have no control over how Codex functions within Xcode. Once again, I say thank you, Apple, for restricting us in every possible way. I am just furious. I do not understand how something this broken can be released. And I am curious how many weeks we will have to wait before Apple finally takes action. Just look at which Codex version is included in the latest Xcode release. We are now on Codex version 1.0.6. Just think about that. An ancient version with no Fast Tier available. But okay, Apple, you must know what you are doing. I am furious, just completely annoyed, and that is all I have to say.
Replies
Boosts
Views
Activity
Mar ’26
Reply to Pls fix m1 chip issues with external monitor hidpi
I just get my M1 Max 16" MacBook Pro and are shocked that I see it do not support 3840x2160 HiDPI with my Apple Pro Display XDR 32" !!! I contact Apple for this issue and they told me, the Pro Display XDR are NOT compatible with M1 Chips !!! Absolute outstanding Information I get. But they will fix that, when does nobody known.  Theres another big issue in compatibility with M1 Macs, the 32" Pro Display XDR does only Show "Million Color" instead of "Billion Color". The Internat Display from new 16" MacBook Pro M1 Max does finally shows itself "Billion Colors" but can not show this on external 32" Pro Display XDR. I report Apple for this issue. Unbelievable for me how this hughe bug can be present!! I'm on Monterey 12.0.1 and the issues is already present.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Nov ’21