I'm looking for an easy way to store contact details from a webapp to iPhone contacts. The UX of this flow from a webapp is far from optimal, therefor I'm looking to utilize App clips in order to do so. From reading the documentation it seems like there is no option to save to phone contacts. Does someone know if this is possible?
Sharing data App clip documentation
Access limitation App clip documentation
Thanks
Long story short, Apple is severely limiting the ability of an App Clip to get at sensitive information (of which the contacts are one of the "sensitive" items)...won't know for sure till they start shipping iOS 14, but you can test it out by setting up a app clip that uses ABAddressBook to set up a new contact and see if it will work. Either A) it won't, or B) it will prompt for permission from the user.
How to use ABAddressBook to do that is explained in this thread
Unfortunately, the answer is still no as of March 2022. If you try to execute a CNSaveRequest, you'll get an error like:
Error Domain=CNErrorDomain Code=100 "Access Denied"
UserInfo={NSLocalizedFailureReason=This application has not been
granted permission to access Contacts., NSLocalizedDescription=Access
Denied, NSUnderlyingError=0x283981680 {Error
Domain=CNContactsFoundationErrorDomain Code=7 "(null)"}}
If you try to request permission, you'll get the same error. By the documentation, I thought maybe there was a chance you could write 1 contact (but not read contacts, thus preserving privacy), but having just written a little test app, that's not the case.
Related
I'm literally going crazy with the new permission system of Facebook.
I am developing a mobile game and I have the code working with the standard access and I would like to start the process to obtain the authorization to use live data but it seem the whole system is broken.
First on some end points like user_friends the Request button is greyed out, it says I need to complete a successful request and wait up to 24 hours, I made hundreds for months it's still locked.
Strange thing it says app review rejected, but I don't remember ever trying the app review and there is no history of it.
So I thought I would try asking for the more basic permission where the button is working, like email and public_profile and it says I must fix the Play store link before going LIVE because it is not accessible.
To fix the link I need to publish an open beta, why is this a requirement? I don't want to do it.
Strange thing I still have a draft of permission request and I have the choice of uploading an apk there, why is it not possible anymore?
Please help
We're trying to use the Facebook Marketing API ads_management permission. We want to use the permission to allow our clients to push the media that was created for them on our app to their personal ad manager
Based on their allowed usage, it sounds like we're utilising this correctly but every app review is being rejected with a fairly generic
Your screencast doesn't show how the use of this permission directly improves the user experience in your app. Unfortunately, we also weren't able to determine this from testing your app manually.
For the first point - our screencast shows a brand/client navigating our app to where all their media lies - connect their facebook account - select the media and then push to the ad manager
This gives us the correct response as long as we use their sandbox environment on the Marketing API
On the second point Unfortunately, we also weren't able to determine this from testing your app manually
We provide test credentials for them to login into our application and go through the exact steps demonstrated in the screencast.
I know these reviews have been giving a number of developers issues but would love to hear if we're missing something really basic in our use because the usecase is really straightforward and not really sure how else to demonstrate it
Thanks
I have integrated FAN with success. I can show banners and interstitials in test and not test mode. So, I have sent impressions to facebook but my current state in the integration shows this:
Shouldn't it be at third step? More Oddly my placements show like this:
So, by the status message it seems it has received requests and this is the only requirement I have found for facebook to start placement review.
So, does anybody know if this is how it works? Shouldn't I be at step 3 (Placements review)?
Thanks in advance.
After uploading the app to live Google Play Store, and wait for a week, I finally get the above screen-shot, without doing anything.
That's means, once you see the ads at your side, the only thing you need to do is to upload the app to live Google Play Store. After that, the only thing you need to do is wait.
It seems I discovered why I could not advance in the review process. Today I got this message from facebook:
Thank you for writing into Audience Network.
I’m happy to explain more about the updated review process for apps.
First, make sure your that the newest version of your app is live in the app store.
Then, once your app has been downloaded by a user and an ad request is delivered, the app
will be enqueued for review. Please note that the review process should still only take 1-2
business days and that this request must be from a user that is not registered
as a developer of the app ID on Facebook.
So, it seems that you need to have your app live and be downloaded by a user that is not registered as developer. This seems not good for publishers because if you have an app that is providing good money you won't see a penny during the review period.
Hope this clarifies the process a bit more.
I had EXACTLY the same problem and my game was live in Google Play with 100+ download.
More then 10 days have passed! But my panel still shows: "Enabled for testing and received ad request recently".
Then I contacted to Facebook and the reply is:
Thank you for writing in. My name is Andrea and I would be happy to
help you! There is currently a maintenance issue going on, which
affected the display of the dashboard. The placement is not displaying
as “enabled” in green, even though your app is approved. However, this
should not affect the ad delivery. Please let me know if you have any
other questions. Have a great week!
In addition:
Before releasing your app to the store, it’s highly important that you
test the integration is working properly. When you run your app on the
simulator, test ads will show by default and indicate a successful end
to end ad serving in your app. When testing on a device however, you
must enable test ads by copying the hashed device ID that is printed
to the console and set it in code via a dedicated function.
And, the most important thing is this:
Until your app is reviewed and approved by Facebook, only the admins
and the developers of your app will be served with Facebook Ads.
To conclude,
App needs to be live before anyone can see the adds except developers.
I am in the process of developing an iPad application for work and have been instructed to provide the following:
"The user must enter their email address to use the FULL application. They must also agree to the terms and conditions, which allows the application to send us the information they enter and give us permission to contact them about that information. If the user does not agree to this, he or she may use a LIMITED version of the application for free."
Does this raise any obvious privacy issues? I understand Apple doesn't like applications to force the sharing of personal information, but if it is optional can that information be used however the developer likes (so long as it is articulated to the user)?
Kind regards
I did the same thing in one of my App, earlier what I did was I forced user to register before using the app. Apple Rejected it and they said registration should be optional and some of the features should be there for the users to be used in your app without registration.
Then I changed my app model to same like yours, I made registration for specific features and in the registration I collect email address and other type of data.
Apple do not have any problem with that. You have to provide a demo account for your App, so that Apple Review team can test it completely.
Thanks, Hope that experience helps :)
You will definitely have problems with Apple. They will reject apps that require users to share information in order use the app (especially if the app features do not depend on an email), and apps that require users to "set them up." If you make the email address optional and allow all users to access the all features of the app, you will not have a problem.
My iOS application allows me to login using my own facebook account successfully. But when I send it on test flight to a friend, the app downloads but when he presses connect to Facebook (which works on my simulator and personal device), it won't let him log in. Doesn't even give him the option to, just spits out an error (com.facebook.sdk error 2). What am I missing? What would cause it to work for me, but not for others? I'm just looking for a general answer here because I followed all the facebook tutorials and I can't imagine what kind of thing could be going wrong.
I just figured out the problem. Should have been SUPER obvious, but being new to development I didn't realize I needed to change the sandbox setting to disabled in order to allow others to access facebook through my app.
This error pops up when your app is not authenticated properly.
You need to keep your BundleId the same at all places.
Change your bundleId in the app that you have registered on Facebook as com.asdad.casd instead of < teamId >.com.asdad.casd