I have been developing an application in iOS using Dropbox Sync API, I am using the API to show a folder´s content in a table view. Today when I tried to sign in with my Dropbox account the modal showed me a message indicating that "The application is not valid". Does anyone knows whats going on?
See https://forums.dropbox.com/topic.php?id=111173. Temporary issue, being fixed ASAP.
Related
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.
My app is live on the App Store and there are no crashes on the front end however when I log in to Firebase I cannot find it on the dashboard. I tried copy & pasting the database URL but I got the message saying that there was an error making the request and that I should try again later. Has anyone else encountered this issue and could advise me on who to contact to resolve it?
According to the Firebase Status Dashboard, there should be no issues with the Realtime Database at the moment.
Assuming that your app was associated with your Firebase account previously and just suddenly disappeared, I have not heard of/ encountered anything similar in the past.
One thing to try is to make sure you are logged into the correct account and have selected the correct project.
Since accessing the database directly through its URL says to try again later, this might be a temporary problem that is resolved shortly.
However to make sure, your best option at this point is probably to reach out to Firebase support directly using this form (requires sign-in).
I've loaded the example app, configured the IDs, and get an app that starts nicely and allows me to logon. Once the logon is complete I get the following message & the app crashes.
Any ideas on what the problem is would be appreciated.
This message turned out not to crash the program after careful review of the template code. Message still displays, but then closes to display the tableView.
I am not able to create oAuth client ID for my iOS app.My app is not create in Apple iTunes App Store because i cannot enter AppStore ID. Here i am attaching two screen shots.First one is create client id form and second one is my error screen shot.How to solve this issue?Please help me..
I am getting error like this....
This a new issue with new google console and happening for around last 10 days for iOS. To solve this for now, go to old console and try with same way you did earlier.
This is the URL for old console(carefully look ?noredirect, this is needed.)
https://code.google.com/apis/console/?noredirect
I am trying to get Open Graph share actions to work on iOS. It's working some what, if I request the open graph url using the Open Graph Debugger first everything works as expected. However if I don't do this the preview in the share dialog is displayed for a seconds or so and then fades out. The post button is also disabled.
What I am seeing in the backend is that if I use the Open Graph Debugger or paste the object url into my own status I am getting requests from a Facebook server (69.171.234.117). However when I share directly from the application I am seeing a request from another Facebook server (173.252.74.115) this server doesn't seem to be able to read the Open Graph data correctly.
Has anyone seen anything like this before or know what's causing it?
EDIT: I've filed a bug with Facebook for this issue. Will updated here if it changes.
EDIT2: Facebook has confirmed this bug and is working on it. The suggested workaround for now is to trigger an initial scrape by using https://graph.facebook.com/?id={url}&scrape=true when the object is created.
EDIT3: Facebook closed the bug report and claimed the issue is solved in there latest SDK. I will verify this and report back.
EDIT4: This seems to be resolved now from my testing.
I encountered this issue before, it turns out that instances of custom open graph objects that are hosted on your server are instantiated only when they are related to for the first time.
Only when the first edge in the FB graph is assigned to your object is it that it obtains an Identifier and it exists in FB's records.
This first edge can only be created using the FB app or the open graph application.
After that's done you will be able to get a unique identifier for your object
GET https://graph.facebook.com/?ids=YOUR_OBJECT_URL
Then you could perform the share using the returned ID
Also see this SO post which supports my claim.