This location specifically seems to be a App Sandbox location, so I suppose the whole problem has to do with the Sandbox. This also is on a byte level the exactly same file as libgd圆4.dylib. The file actually gets copied to two other places as well. directory with the working one, the file still gets marked as damaged, even though it worked a second earlier outside of that location. And when I manually replace the broken file in the /private/var/folders/. When I compare(with the diff command) the file to the original file in the package I sent to App Store Connect, there is no difference at all. This is weird to me for multiple reasons. “libgd圆4.dylib” is damaged and can’t be opened. When I try to pen this file in any capacity, e.g. When I click "Show in Finder" I get taken to this folder: Contact the developer for more information.
“libgd圆4.dylib” can’t be opened because Apple cannot check it for malicious software. But when I try to open it I get this error: I have an MacOS App that get's accepted by Transporter/App Store Connect and is available to download in TestFlight.
It's literally every single Xcode update that comes out.Ĭome on Apple, give the developers (who help support your ecosystem) a hand here. How can such a large company have such an issue with file distribution? I feel like a pretty competent individual and I've yet to find any reasonable way to deal with these updates.
This is now on 2 completely different ISPs. Start it up again and let it run overnight.ĪGAIN it gets ~95% complete and errors out. So I decide whatever, I'll try it on my home internet connection. Check bandwidth again and no issues on my end. Well, same problem with TERRIBLE download speed. I let the download do its thing, but of course it errors out right at the end and the download somehow is corrupted. Note this is trying to download directly from the App Store. Why? I run a speed test and our bandwidth is perfectly fine. The download gets limited to ~700KB/s with occasional spikes around 2MBps. I've tried the download on the internet connection at the office (Spectrum) which has download speeds well past 100Mbps. I've been trying to update to Xcode 12.5.1 since yesterday now. The problem is that these mirrors can contain malicious versions of Xcode which inject malware into built apps. For those unaware, the short version is Xcode downloads are notoriously slow from Apple's servers to the point that a lot of people end up trying to find other mirrors for the MASSIVE 10+GB updates that come out. I'm sure most of us are aware of the XcodeGhost issue from awhile back. Var upClick = CGEvent(mouseEventSource: nil, mouseType: mouseTypeUp, mouseCursorPosition: location, mouseButton: mouseButton)! Var downClick = CGEvent(mouseEventSource: nil, mouseType: mouseTypeDown, mouseCursorPosition: location, mouseButton: mouseButton)!
Here's the code snippet that actually clicks the mouse:
Is there an approved, official way to programmatically click for users? There are tons of auto clickers on the Mac App Store, so I'm a little confused as to why I'm being rejected now. I'm currently using a CGEvent.post() to click automatically, and this requires Accessibility permissions to work. Specifically, the app uses Accessibility to keep the mouse active, which is not the intended use of the Accessibility API." "Your app uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1 of the App Store Review Guidelines. However, I just submitted a new update and was binary rejected for the following reason: Hi there! I published an auto clicker app on the Mac App Store about 7 months ago with no issue. Unfortunately, since the value is always "1.0" in the sandbox (including TestFlight) I don't have a good way to test this.ĭoes anyone have any real-world experience that can shed light on what format I can expect? My instinct is that the store is determinative, and thus to expect the macOS CFBundleShortVersionString on the Mac. I'm unsure which value to expect in Mac Catalyst, since it's a UIKit (and thus iOS)-based app being distributed through the Mac App Store and run on a Mac. In the sandbox environment, the value of this field is always “1.0”. This corresponds to the value of CFBundleVersion (in iOS) or CFBundleShortVersionString (in macOS) in the ist file when the purchase was originally made.
In the Receipt Validation Programming Guide, the field's notes are as follows: I want to use the original_application_version value from the app receipt to grandfather some features for users who are first-time users vs existing users.