Post not yet marked as solved
Hi there,
Thanks for your question. You might have better luck asking this question over in Apple Support Communities run by Apple Support.
—Jason.
Post not yet marked as solved
Hello Inzi1812. As you control which frameworks are included in your app, you are responsible for all functionality of those frameworks, whether you use it or not.
You will want to individually review each framework you include in your app to determine if it has a requirement for the microphone. If you're using third-party frameworks, and you're unable to identity microphone usage directly, you'll want to ask the provider of those frameworks.
You will also want to review the functionality in your app to ensure it doesn't actually include microphone functionality. For example, if your app includes an option to do a voice search, that requires microphone access.
—Jason.
If you're building an MDM solution that others will be paying to use, this is a non-trivial project, and requires significant technical knowledge of servers, security, REST endpoints, back-end databases, and more. Most people looking to build an MDM solution already have a solid idea of where they should be starting.
Perhaps instead you're looking to manage devices in your organization, and you're looking to learn where to start with device management.
Can you clarify which path you're on? The guidance is significantly different.
—Jason.
Post not yet marked as solved
Hello Oliver_Tong. The error message tells you want to do here:
include all of the “UIInterfaceOrientationPortrait,UIInterfaceOrientationPortraitUpsideDown,UIInterfaceOrientationLandscapeLeft,UIInterfaceOrientationLandscapeRight”
Basically, you need to enable all the options in the "Supported interface orientations (iPad)" for your target. This is the default.
The iPhone entry also defaults to all except "top home button".
Basically, you should not force "only portrait orientation". Apps are expected to run on all available devices and support multitasking, and that means having flexibility in your layout.
I recommend reviewing the Apple Human Interface Guidelines on Multitasking and Layouts
—Jason.
Post not yet marked as solved
My general recommendation: If you ask if you should give credit, give credit. It costs you nothing and demonstrates integrity.
Something as simple as "Inspired by..." or "Based on..." could work well.
It depends on how similar the images are, and whether someone might confuse your image for the original.
Be sure to check the license for the "free" art, too: Some may require attribution for any derivative art work, and have specific language for how that is done.
—Jason.
Hello Leo6Leo,
CallKit requires a network connection, and that is not allowed per the rules.
Your creation should not rely on a network connection and any resources used in your app playground should be included locally in the ZIP file. Submissions will be judged offline.
—Jason.
Post not yet marked as solved
Hello TaoDu, I assume you mean the Family Controls entitlement?
If so, each entitlement has its own review process and timeline. Depending on the volume of requests, responses may take longer than expected. The team should contact you with further instructions if there are any issues with your request. Otherwise, you can expect to be notified when your request is approved or declined.
Follow up with your original entitlement request to determine its status, provide more information about why you need this entitlement, or to learn why you were not approved. Submit a new request only if you’re unable to follow up with the current one, but be aware doing so may delay your request further.
—Jason.
Post not yet marked as solved
Hello. Please review the Apple Developer Program License Agreement, which describes the legal terms under which Apple Maps Service can be used. If you have any questions about how to interpret this Agreement, please consult your legal counsel.
—Jason.
Post not yet marked as solved
Normal response times is "typically within three business days", which can vary depending on volume, complexity, and a variety of other reasons. While it's rare that you don't hear a response from a DTS engineer within that time, it does sometimes happen if the team is especially busy.
TSIs are reviewed by one or more DTS engineers before assigned. The initial response may be a request for additional information because the engineers who reviewed it determined they didn't have what they needed to start their investigation. That initial response may be pre-written, but is specifically sent after an engineer has reviewed your question.
—Jason.
Post not yet marked as solved
Hello JohnLove,
I took a look, and the last email from us was sent on March 10, confirming that we need a focused sample project in order to provide support. This was the same request, and for the same reason you were asked to provide it in the related Dev Forums post.
DTS provides code-level support, and needs a reproducible project to determine if the issue is in your code or in the system.
—Jason.
Post not yet marked as solved
Hi Stew, thanks for the Case ID and the additional context.
I can confirm that the case is assigned to a DTS engineer, and it's a matter of making their way through the rest of their requests to get to yours. My apologies for it taking as long as it has, but as I alluded to, the team is very busy right now.
That said, I'm unsure if it's a question DTS will be able to help you address, as the issue seems to be specific to Logic (rather than your code). Of course, this is a preliminary look, and I'm not by any stretch a CG expert, so there may be something you can do differently or instead. A DTS engineer will make that determination once they get to your case.
As an aside, I also took a look at your feedback reports, and all of them are with the appropriate MIDI teams. I wouldn't expect a "near term" resolution; it could be several months, a year, maybe more before it's resolved (assuming it is at all).
—Jason.
Post not yet marked as solved
Hello StewMacLean, if you share your Follow-up or Case ID number, I'm happy to take a look.
Normal response times is "typically within three business days", which can vary depending on volume, complexity, and a variety of other reasons. While it's rare that you don't hear a response from a DTS engineer within that time, it does sometimes happen if the team is especially busy.
Thanks,
—Jason.
Post not yet marked as solved
Hello eightycrazy. I'm not aware of any Apple APIs for sharing a text message from the Messages app, nor for automatically sending text messages.
You may want to consider filing a suggestion requesting such API. You can do so using the Feedback Assistant app or website.
Please include a detailed explanation of the functionality you are suggesting, and the impact on your app or customers of not having such functionality.
The relevant engineering and product marketing teams will evaluate your suggestion.
You can add your Feedback number (FBnnnn) to this thread for tracking purposes.
—Jason.
Post not yet marked as solved
Hello AnonymousAnomaly,
Product feedback should be submitted via Feedback Assistant app or Feedback Assistant website. If you do not have a developer account, you can also submit your feedback via Product Feedback
—Jason.
Post not yet marked as solved
Hello Shabari, a couple of things:
The "unsubscribe" link cannot be removed. I would encourage you to file an enhancement request (ER) asking for the ability to do so. You can file that ER via the Feedback Assistant app or website. Please include justification for wanting to remove this link, especially because....
An "unsubscribe" link is likely required because of the email may be classified as "commercial", and thus would require such a link. One possible solution here may be to provide a customizable link, rather than removing it completely. That would be up to the relevant engineering teams to discuss and decide as part of your ER.
Please add your Feedback number (FBXXXX) to this thread for tracking purposes.
—Jason.
