5.1.1

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

My question requires an interpretation of the language in 5.1.1 (iv) because I will be using the Google UMP to collect UE GDPR for my ads that are served from AdMob. Non-UE users will still default to Apple's ATT. Effective in January 2024, if GDPR consent is not fully granted, or if it is not specifically configured using Manage Options in such a way as to allow AdMob to serve ads, no ads will be delivered from AdMob. The user-interface from the Google framework is so complicated and convoluted that it will be virtually impossible for a user to define the correct configuration - even if they want to. That being the case, any selection other than Consent will effectively disable ads from AdMob; thus preventing developers (who rely on AdMob) from generating ad revenue when GDPR applies. My question is whether it is acceptable under 5.1.1 (iv) for me to restrict access to my app unless the user provides the necessary consent to meet AdMob's requirements? Would restricting the app to a limited

Hi somprabhsharma, Please review the App Store Review Guidelines for the requirements of Legal, Data Collection and Storage, and Sign in with Apple—under 5.1.1(v, ix). You may need to seek legal counsel to determine the appropriate next steps for your app based on the regulations and the compliance in your region. Note: App Store Review does not pre-approve, nor pre-review app submissions, so your developer team and/or counsel will need to submit a production-ready app for review as specified in the guidelines above. Cheers, Paris

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