This issue was mentioned in this WWDC video. It refers you to this older video from WWDC 2020. You already mentioned two of the other links I was going to refer to you. I tried your app and it said it ran to completion with no error. It doesn't seem like it should work at all since you don't seem to have the proper entitlement and usage string. I thought I had changed the destination IP to be a local IP address. But I was testing in a VM, so maybe the networking is too funky and it was treating it as an internet connection. You don't need to be administrator to approve local network access. Obviously, for issues like this, Apple does not provide any way for an app to bypass user consent. That would defeat the purpose. Apple does usually provide some MDM key to preset the value for managed devices. If this is library code, I don't see how it would be a problem. It's the app developer's responsibility to manage this.

I can reproduce what you are seeing. Try adding the following to the map view delegate: func mapView( _ mapView: MKMapView, regionDidChangeAnimated animated: Bool) { addScale() } I tried your code, making PISimpleMapView its own delegate, and it seems to fix the problem.

Sorry. I only looked at the other app. I missed that file. However, I looked at the file and, other than the version number, it looks like XSLT 1.0. I changed the version from "2.0" to "1.0" and ran it against some sample data posted by acmuller and it seems to work fine. I admit that I'm not familiar with XSLT 2.0. There may be some differences in behaviour even if the syntax is identical, but it seems like you can just change the version number back to "1.0". Unfortunately, after looking more closely at this project, it seems much more problematic than I originally assumed. I thought this would be a straightforward code-level question involving one of my favourite technologies. I was wrong. So, I don't know what to tell you. Symbol conflicts between your code and any private frameworks are easy to fix. Apple only officially supports the public APIs as documented on the Apple developer site. Internally, Apple may implement those APIs with various other 3rd party frameworks, but you can't use those. It's always possible to have a symbol conflict between Apple's private frameworks and your own code, but you can just rename the symbols in your code. Going beyond code-level issues, I see a couple of potential problems getting the app published in the App Store for iOS. But I'm not Apple, so all I can do is speculate and that gets messy in a hurry.

I downloaded your existing apps and all of the XSLT files are 1.0. Can you confirm that you are re-implementing the XSLT operations as 2.0? And can you confirm that you absolutely, desperately need XSLT 2.0 support and no other solution will suffice? XSLT 2.0 is usually only used via Java, in a server context, and only in a handful of very specific, XML-friendly industry domains. This is the best reference that I've seen for XSLT version support: (https://stackoverflow.com/tags/xslt/info/) I don't know what you mean about that external C library that is no longer acceptable in the App Store. The only reason I could think of would be a GPL-licensed project. If that's the case, then the App Store isn't the problem, it's the license. The GPL license is designed to prevent you from using the code with Apple platforms. Releasing such code in the App Store would be a violation of the license. That makes the app illegal and Apple doesn't allow illegal apps in the App Store. From my casual inspection of your app bundles, it seems that XSLT may only be a tiny part of your apps. It doesn't sound like trying to support XSTL 2.0 is worth the effort. If there was something specific you need that XSLT 1.0 doesn't provide, maybe you could implement your own EXSLT function. Anything that Apple provides is going to be XSLT 1.0. There really isn't any WebKit interface per se. I think that just refers to the standard XSLT HTML stylesheets that I think all web browsers support. There's no point in trying to do XSL via Javascript in WebKit. That's just a Rube Goldberg architecture. My software makes very heavy use of XSLT and all of it is XSLT 1.0. You can do pretty much anything in XSLT 1.0. Certain things may be easier to do in XSLT 2.0, but the effort required to support that far exceeds the gain in convenience. And if you are willing to write some EXSLT, then there's virtually nothing that you can't do in XSLT 1.0. Apple has some native XML and XSLT APIs available: (https://developer.apple.com/documentation/foundation/archives_and_serialization/xml_processing_and_modeling/) Personally, I don't use Apple's APIs. The DOM processing APIs, which include the XSLT logic, are macOS-only. It was quite easy to implement my own, more powerful, wrappers around the lower-level APIs provided by libxml2 and libxslt for parsing XML and transforming XSLT. I do all of the XML generation logic on my own. I've only written EXSLT functions in Perl, where they are very easy. They are probably much more difficult to implement in C. I certainly wouldn't consider Apple's Objective-C API, or the lower-level C APIs, to be "unsafe". They are C-based, so you have to be careful. You may get some minor memory leakage in instruments, but not enough to worry about. The biggest problem is that they are Mac-only and essentially forgotten. Apple doesn't pay much attention to them and neither do most app developers. Using the lower-level C APIs provides some insulation against potential deprecation and removal of the Apple wrapper APIs. I'm not sure what you mean about a "clear statement in the reference documentation". XML, and by extension XSL, are not "popular" technologies, in the social sense. While they are widely used in many industries, you won't find much about them on the internet except as fodder for mocking older developers. There is very little overlap between XML and the practice of most app developers for Apple platforms. It is safe to assume that everything is XSLT 1.0 and will always remain so.

Is there no way to find threads you previously participated in, other than to bookmark them in your web browser or something? Nope. The only reference to my past activity seems to be on my profile... which only mentions the number of posts I made, but doesn't mention what or where they are or provide any way to find them. Yep. On the bright side (?), it is so difficult to find new threads in over 300 separate forums that you are very unlikely to actually participate in multiple forums. So just bookmark your favourite tags and go to those to see if there is any new activity in your threads.

I guess I will be Etresoft now. I need to use my Developer account to upvote or downvote. And I need 100 points to do that. <sigh> Those 971 points in the other account aren't going to help.

There are no exact breakdowns available via the Apple Developer Console that provides developers with a full breakdown of who pays what. It isn't in the developer console. It is in the Apple Developer Program License Agreement. - https://developer.apple.com/services-account/agreement/XV2A27GUJ6/content/pdf I have read if you are a developer selling apps in the UK, there is no VAT to pay as Apple handles it. Whereas I am read Google Play don't handle any VAT. You will have to ask Google how their system works. Is anyone able to clarify this point for me? No. This is an anonymous support forum. No one knows where you are located or what your particular tax structure might be. The rules could be different for you than they are for someone else. This is what makes global sales taxes such a challenging issue. Please review the Apple Developer Program License Agreement that I linked to above. If you are not able to figure out what your tax obligations are, then you will need to hire a tax attorney to help.

Can you share some documentation regarding this path? Here is Apple documentation. - https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Tasks/InstallingFrameworks.html One concern with this approach is that other installers can overwrite some common library I suppose that is possible, but highly unlikely. There are really no such things as "common" frameworks. (eg libcurl.dylib, assuming we can also place dylibs here).  That path is only for frameworks. If you have stand-alone dylibs, a more appropriate place would be /usr/local/lib. However, in /usr/local, you stand an excellent chance of some other installer overwriting a common library, or of the user deleting it. libcurl, however, is part of the operating system. You don't need to install that. If you did want to install your own build of libcurl (which wouldn't necessarily be a bad idea), the best approach would be to create your own framework and statically link that to your custom build of libcurl.

Thanks a lot for the replies and thoughts. Do people have favorite resources for learning the ropes as a small business? I've been reading "Small Time Operator." I know of no such resource for app developers. Moreover, most of the information that you will find about starting an indie app development business is wrong, sometimes maliciously wrong. Developing software is not like other businesses. When you go to talk to an accountant, lawyer, or insurance broker, you have to explain it to them from the ground up. In many cases, they will have never encountered anything like this in their careers. When you fill out forms, you will struggle to even find the right category to identify your business type. When you look to find out what tax and consumer protection laws apply to your business, you will have to go deep into the minutiae of intangible personal property and/or software services. Most of what exists for "software" is designed for companies like IBM. Either it will not apply to your small company, or it will, with all the paperwork, fees, and forms that IBM has to submit. It was easier years ago when it was more of a "Wild West". Now, all of the authorities know something is going on, they know they are being cheated, and they are looking to get control. However, there is one bright spot - Apple. We will soon see the end of the Golden Age of the app developer, but it isn't over yet. As bad as it is, Apple is as good as it gets. Apple takes care of most of the details and gives you access to the best customers. You should be able to find professional services like accountants, lawyers, or insurance brokers who know about Apple's developer program and maybe already work with some Apple app developers. Keep looking until you find them. You might have to choose some bigger, more expensive names than you would like. But the bigger companies have more resources to tap into than the local folks who just deal with plumbers and duct cleaners. If they don't know how to do something, they have people they can call and ask. I can't make any guarantees about the future. There are a lot of powerful and/or influential people who are working hard to put an end to this. They've made their money and now they want to burn it all down. Don't follow their advice.

Build settings reference - https://help.apple.com/xcode/mac/11.4/#/itcaec37c2a6

Can I use any timestamp server with codesign command? Apparently If yes, can you please share list of trusted TSAs? You mean other than Apple? Trusted by whom? The codesign command does support a timestamp server parameter. If you trust the server, then you can supply a parameter. I have no idea if it works or not. Also, will notarization succeed if I use non-apple timestamp server? Utterly no clue. Given what I've seen regarding Notarization problems, this seems like a high-risk approach. Notarization is drop-dead, fall-of-a-log, Oh My God This is Easy! Yet some people insist on trying new and unusual ways to build code and attempt to notarize it. Each new failure is more comical and bizarre than the last. If you sincerely think it would be a good idea to use a custom timestamp server and to attempt to notarize software with it, why don't you just try it and see if it works? What's the worst that could happen? Your download displays a big "cannot check for malware" warning? Some minor operating system update causes your app to stop working? Your app stops working on its own on some random date in the future and no one know why? Your customer band together and file a class-action lawsuit? How do I specify a timestamp server in productsign command? I see no timestamp server option in the productsign command.

This is the developer forum. All answers will require you to use programming instructions of some kind. That's the whole point. You should probably post your question in Apple's Consumer support forums instead: https://discussions.apple.com/welcome Those consumer support forums are much, much larger. Instead of waiting days (or forever) for an answer, you can expect an answer in a few minutes. You just have to make sure to pick the appropriate forum and provide a good description of the problem. Sometimes, the big forums are so busy that questions don't get answered in a few minutes and they fall off onto page 2, where no one will ever look for them. After 24 hours, an Apple Community Specialist will offer you a couple of Apple Support articles that might or might not help.

Apparently, this is a known bug: https://developer.apple.com/forums/thread/668919

You can assign a background quality-of-service to these tasks. That should keep them on the high-efficiency cores. See the documentation. - https://developer.apple.com/documentation/os/workgroups/tuning_your_code_s_performance_for_apple_silicon?language=objc

I believe you can do that using MDM. However, macOS is a consumer operating system. That is what it is designed to do. It may be possible to turn off various parts via SIP, but I don't know. If you wanted to use it for this kind of work, you will likely have to find some other way.