Hi,
I suggest Apple to more frequently reply to software developers. My previous replies didn't get any reply or help from Apple. Also many questions from other developers were not answered. I guess that so large company can pay more attention to their sofware developers. We really need more help and replies from Apple to create good software apps for macOS and iOS.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
We simulate Gaussian blur as a Box Blur with complex shader (several passes on two axises) using Metal on Mac.
I noticed slight fast pulsation of picture brightness when we reach radius more than 16 pixels in a fragment shader (we read 32+ pixels from a source texture to calculate 1 output pixel). We use float4 calculations.
This issue appears only on M1 Mac and only after sleep. The problem dissappears after restarting macOS. And no problem on Intel iMac with AMD graphics.
These artefacts appear in macOS Monterey 12.4 and also in macOS 13 Ventura Beta 1 on M1 Mac mini. We don't have any problem with other more simple shaders.
Hi,
I recently created and installed new code signing certificates/keys on my main Mac.
How to easily copy these certificates/keys to my another Mac with the same Apple ID?
Earlier Quinn suggested:
"The easiest way to do this is use Xcode’s import/export feature. Launch Xcode, choose Xcode > Settings, select Accounts, select the account in question, then choose Export Apple ID and Code Signing Assets from the action (…) menu."
And it worked fine in 2020-2021. However import/export options are no longer available in XCode 16 anymore.
Please suggest a simple solution.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Is it possible to find deprecated functions without Xcode in runtime?
I have a project which doesn't use Xcode to build the code for macOS. It would be great if I could see logs in Terminal when deprecated function is called.
I compiled a dynamic library for macOS (open source) When I checked with
otool -L abc.dylib
it shows that it links several other libraries from /usr/lib/
Is it OK, or Apple may remove these libraries in future versions of macOS?
/usr/lib/libz.1.dylib
/usr/lib/libiconv.2.dylib
/usr/lib/libSystem.B.dylib
/usr/lib/libbz2.1.0.dylib
/usr/lib/libobjc.A.dylib