I have an app through which user can share on twitter. Everything was going great few days ago but suddenly, I started receiving permission errors. I checked my permissions but surprisingly, I got this:
Permissions are also set as read write but still I am getting error on sharing.
I don't know what is wrong. Any suggestions?
This has happened to a number of developers - see https://twitter.com/TwitterDev/status/473547632669782016
If your application lost write access this week-end and you believe this is an error, please fill https://t.co/jUQPuVHhyo (3rd option).
Related
I am trying to integrate Facebook Ads in my iOS App.
I have the SDK installed and I also already receive test-ads. So everything seems to work fine.
BUT...
On the Facebook page inside the Monetization Manager there is a 4 step tutorial on what I need to do.
was Choosing the ad format -> Banner -> Done
Integrating the SDK (I'd say it's done cause I see Test-Ads inside my app) but here's the problem... Cause there is no Checkmark there.
Is the payment info. That's done.
Would be the Review that I'd like to do, but that seems to be deactivated...
So... It also says there, that I need to be logged in to facebook on my phone with an associated Account. I am!
I don't know what else I'd need to do in order for Facebook to recognize that I already successfully displayed a Test-Ad and I just can't find any contact phone number to ask somebody.
Any hints are very much appreciated.
Btw. I already tried yesterday evening (in case the activation process simply takes longer...)
I finally found the Problem after trying every single Setting on the Facebook page...
The problem was that I added my device as Test-Device.
So after removing FBAdSettings.addTestDevice(FBAdSettings.testDeviceHash()) it was working.
Did cost my a lot of time and nerves :) But now everything works as expected!
Whenever i try to navigate to App-Specific Shared Secret within ItunesConnect the dialog box attempts to load briefly then I get directed to a crash page titled
"We can't process your request".
I've reset safari clearing all website data and also used other computers.
I've contacted Apple who are sending an email shortly requesting more information but wondered if anyone else had come across a similar fault?
Another very easy solution which worked for me:
Use safari
SOLVED
The problem was due to not previously having created a master shared secret.
Once I did this then I could generate the shared secret for the specific application.
I has a similar issue, when I was getting invited to join Apple Developer Program. I tried joining through the invitation link and I would always get the "We can't process your request" message.
The solution was to:
Log in to an iPhone/iPad with that particular Apple id.
Try to install an app.
You will get a terms and condition pop up that you should accept.
Install the app
Wait for a while until Apple fast servers update your status (around 1 hour for me)
Now you should be able to proceed without the weird message.
I think need to update Mac OS to latest will solve problem. Alternatively you can use google chrome browser.
A few days ago, Apple rejected my app, indicating that it didn't have IPV6 support, however I don't need that support since my app does not require internet access.
I asked the following:
Hi, my app does not need any internet connection yet.
So, why it's required to have support to IPV6?
They said:
Thank you for your response and for your question. In order to bring your app into compliance with Guideline 2.1 it would be appropriate for your app not to crash when logging in.
end
So, why do I need that Support?
If is necessarily, how do I can do it?
Please I need help
Test your app extensively and fix the crash. Enter wrong values, don't enter anything at all, intentionally try to break your app and get it to crash. Then you will find your error and you can fix.
EDIT BASED ON COMMENT BELOW
"My app don`t need conect with external database, because I got the information inside" - in this case, no, you do not need to add IPv6 support because you are not communicating with the internet for logging in purposes.
You can keep the login given it is only going to be 2 people using the app, just resolve the crash when logging in.
To test, enter a variety of incorrect passwords and usernames to ensure that there is no crash on incorrect entries, and confirm that correct entries do not crash the app.
Original Answer
Apple indicated that because there is a login feature, they think it is trying to communicate with an external database (ie a database that is not on the device). If there is no external database, just fix the crash is what they are asking.
Based on your question, you have eluded to the app not communicating externally for logging in. While some may find this odd, it is not uncommon. An example for those wondering would be a childrens app for iPad. The iPad might be shared amongst several children and as such each child might complete different sections or features of the app so an account local to the device is a good idea if there is no cloud support.
If there is external communication, you need to handle the case for no internet access. The question has been answered extensively, however this was the first result I found:
Detect Internet Connection and display UIAlertview Swift 3
Update: Why do I need to Support the case for no internet connection?
A use case:
John has just downloaded your app. He has just walked through the steps to create an account, but he has accidentally set his device to Aeroplane Mode.
John hits the "Create Now" button but nothing is happening. There is no error or success alert appearing, the screen has not changed, he can't see a loading icon. John is confused and getting frustrated because he's certain that he has completed everything in the form.
John doesn't understand that he needs internet connectivity to successfully submit a request to create an account. John decides to delete your app from his device and leaves a bad review.
John really could have used an alert saying "You need internet connection to sign up to this app. Please check you are connected and try again". This would have made John a whole lot happier and he probably would have continued to use your app with all of it's amazing features.
More information can be found in the guidelines that Apple mentioned, and further to this, the Apple Design Principles Guide is an invaluable resource.
I hope this makes sense.
I have an iOS App on the App Store, and it connects to Google Drive. In the past week or so, I've noticed two new problems in my live app.
The App suddenly stopped logging in. I would get a 401 - invalid_client. I found a lot of questions/answers for this problem, but they were all for people who couldn't get it working. Mine was working for about two years and then stopped working a couple of days ago. After trying a lot of things, I found that I was using <id>#developer.gserviceaccount.com as my Client ID, and when I changed it to <id>.apps.googleusercontent.com it worked again. I don't know why this change fixed it, and even knowing that this fixes it, I can't find if this is the correct/appropriate solution.
I explain my second problem, which is very specific here, but skip to the next paragraph to get to the point. The second issue is a a result of Google changing the way their API calls respond, and this is why this wasn't an issue when we submitted the latest version of the App to the App Store. Google has changed the way the explicitlyTrashed property of their GTLDriveFile class. Per their spec, this property should be either an NSNumber containing Yes, or null. They have recently changed it so that it is always an NSNumber set to either Yes or No. This is what's breaking our functionality.
Anyway, these are two changes Google has made on their end recently that currently has my customers on hold since I have to fix this and push it out. My question is if there's a place to keep up with these changes that Google is making recently. Also, if someone knows or can point me to why the first issue is happening, I would greatly appreciate it.
For the first issue, the reason why it got resolved by using [id].apps.googleusercontext.com is because it it requesting an authorization token from an app to the server, as opposed to a Server to Server transaction using impersonation ([id]#developer.gserviceaccount.com). This is the right solution for both android and IOS apps requesting a token.
As for your second question, the best way to keep up to date with the latest changes is through their official blog: http://googleappsdeveloper.blogspot.com/
Another resource is the G+ Google Drive Developer community: https://plus.google.com/communities/107264319205603895037
I implemented Facebook login a while ago in my app, using the Parse tutorial:
https://parse.com/tutorials/integrating-facebook-in-ios
It seemed to be working just fine, and I released my application to the app store. I then changed, on my Parse dashboard, the app from regular to "Production", and I was wondering if this could cause my Facebook login to stop working.
The actual error message on the phone, which occurs after a user presses the Login button, then after hitting accept for the basic facebook permissions, it brings up an error message:
Could it be the production switch, or is there something else wrong here?
I think there are just two things that should cause this error. First and most possible one is the one you thought of it, so switching to the production. And the second could be some similar setting on facebook developer site. You shoould check there if the settings there are in production environment. I know I dont give you anything specific but I'll for problem there if I'll have the same problem.