5.1.1

>I didn't found any info in the guidelines about thisAre you sure? There are two parts to your proposal: ✖ login to access the App and ✖✖ use of OAuth2/restful (web session/simplified) token v. sign in/pwd.See the ASRG's section 5.1.1:(v) Account Sign-In: ✖ If your app doesn’t include significant account-based features, let people use it without a log-in. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, Twitter, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality. The app must also include a mechanism to revoke social network credentials and disable data access between the app and social network from within the app. ✖✖ An app

El 19 sept. 2020 a las 18:39 De Apple Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requests the user’s consent to access their camera but does not clarify the use of the camera in the applicable purpose string. El 19 sept. 2020 as19:03 Hi, we recently sent a previous version that had the same requests in the .plist file informing the use of the camera to be able to exchange your photo and it was approved without problems, none of this has changed. I send a screenshot to confirm this. Captura de Pantalla ... El 19 sept. 2020 a las 19:54 De Apple 5. 1.1 Legal: Privacy - Data Collection and Storage 4. 8 Design: Sign in with Apple Hello, Since your app offers account access through a third-party login service, Sign in with Apple should be included as an equivalent log in option. Please review Guideline 4.8 for more information about our Sign in with Apple policies. To learn more about implementing Sign in with Apple in your app, we recommend you review the samp

Please forgive the late reply, I've done some additional research during Spring Break here, and it's been instructive.Since we started this process, DisplayLink has released 5.1.1 of its kext, and the installer that they have posted is supposed to be notarized. Looking at the package:Persephone:Extensions tom$ spctl -a -t install -vvvv /Volumes/DisplayLink Installer/DisplayLink Software Installer.pkg /Volumes/DisplayLink Installer/DisplayLink Software Installer.pkg: accepted source=Notarized Developer ID origin=Developer ID Installer: DisplayLink Corp (73YQY62QM3)However, the package itself doesn't have a ticket stapled to it, which means that you must have access to the internet if you want it to install correctly. The spctl action itself isn't enough for you to know you have a viable package that will install offline. However, it appears that stapler can tell you:Persephone:Extensions tom$ stapler validate -v /Volumes/DisplayLink Installer/DisplayLink Software Installer.pkg Processing: /Volumes/Dis

Hi, I just ran into this issue on an M1 14 MBP. I got it to install and run correctly. Instructions here. The key is for now it needs jaxlib 0.4.10 but jax 0.4.11. Jax seems to allow using a jaxlib that is one point version less, so this configuration works. The key instructions are below: # obtain JAX source code git clone https://github.com/google/jax.git --branch jaxlib-v0.4.10 --single-branch cd jax # build jaxlib from source, with capability to load plugin python build/build.py --bazel_options=--@xla//xla/python:enable_tpu=true # install jaxlib python -m pip install dist/*.whl You also need Bazel 5.1.1 to build jaxlib (it’ll give you instructions if it can’t find it) and Python 3.10 or it won’t install the jaxlib wheel. If you’re using Anaconda you’ll have to create an environment using 3.10 and not any other version. At this point it tells you to install Jax via pip, but don't do that or it will default to 0.4.10 which is the wrong version. Instead, download the zip for the source code for the

I also do not save the token obtained with apple Sign in on my app. I could start saving it and revoke it when the user wants to delete the account, the issue is I always get invalid_client error no matter what client ID I use in the request. This is the last part in the Apple reminder email. If your app offers Sign in with Apple, use the Sign in with Apple REST API to revoke user tokens. https://developer.apple.com/documentation/sign_in_with_apple/revoke_tokens#discussion Is this really necessary to pass the app review? The token as a validity of 1 day, and users are not going to create and delete an account in the same day I guess. It seems that this API isto be used when using sign in with apple on the web. Can someone at Apple provide some explanations? Upcoming Requirement Reminder Note: This is a support message regarding upcoming requirements that may be relevant for your app. Starting June 30, 2022, apps submitted to the App Store that support account creation must also include an option to initiate a

Hi, I just ran into this issue on an M1 14 MBP. I got it to install and run correctly. Instructions here. The key is for now it needs jaxlib 0.4.10 but jax 0.4.11. Jax seems to allow using a jaxlib that is one point version less, so this configuration works. The key instructions are below: # obtain JAX source code git clone https://github.com/google/jax.git --branch jaxlib-v0.4.10 --single-branch cd jax # build jaxlib from source, with capability to load plugin python build/build.py --bazel_options=--@xla//xla/python:enable_tpu=true # install jaxlib python -m pip install dist/*.whl You also need Bazel 5.1.1 to build jaxlib (it’ll give you instructions if it can’t find it) and Python 3.10 or it won’t install the jaxlib wheel. If you’re using Anaconda you’ll have to create an environment using 3.10 and not any other version. At this point it tells you to install Jax via pip, but don't do that or it will default to 0.4.10 which is the wrong version. Instead, download the zip for the source code for the

Thanks a lot for your response. I don't think that's the point. In fact, your app accesses potentially sensitive user information. I think that's the problem. It does access it, because the company offers a free and open API to encourage third parties to do that. But keep in mind this rule is under section 5.1.1: Data Collection and Storage. My app does not collect or store anything, at all. It's merely accessing the data from a GET endpoint, showing it to the user, and discarding it. I don't even have an account or login system, or even any kind of telemetry. The user just looks at their account data through my app, with their token, then it's gone. Much like a web browser. Are we sure this rule doesn't apply only to apps that actually collect and/or store data? Reading AppStore rule, the app should be submitted by the official firm. It cannot be by an individual developer or by a company that is not a banking or financial service company. Then how do financial aggregators do it? Or regular portfoli