I wrote a program to upload our racing videos continuously (loop through every five minutes to see whether a video is finished upload, if finished then start upload another race video)
It all works fine and just from yesterday, it suddenly give a credential exception. First I though it might be the google blocked me cause I uploaded too many videos?
So I tried our testing google account use the program to upload one video and it comes with the same error again?
Some body know anything might go wrong? To me the code is absolutely fine, It works for nearly a year and no body touched it.
I'm confused!
Crash point is --> call service.setUserCredentials( username, the_password)
Java exception thrown: com.google.gdata.client.GoogleService$InvalidCredentialsE
xception: Invalid credentials.
It magically works today. I still don't know why, I think its google's problem down there end, so if anybody met this problem in the future, don't panic, go home and have tea, try tomorrow~~~
Related
I set up an advanced app clip experience to be triggered by a URL in the form
https://domain/pf
and I am actually expecting it to be triggered by a number of URLs in the form
https://domain/pf/[uuid]
The app clip is correctly triggered by the exact "https://domain/pf" URL but not by the "https://domain/pf/[uuid]" URLs. Since the first URL triggers the app clip, I assume my .well-known/apple-app-site-association is correctly configured.
According to the original WWDC video on app clips (1) and to the official documentation (2) one should be able to catch all sub-URLs for an app clip experience.
Does anyone have experience with this?
Thanks!
Alessandro
(1) https://developer.apple.com/videos/play/wwdc2020/10146/
(2) https://developer.apple.com/documentation/app_clips/configuring_your_app_clip_s_launch_experience
For the benefit of everyone who has the same issue, what I described above is now working.
I don't know the exact cause but I assume it's due to propagation of the information through the Apple servers.
The app clip (QR codes) started working after about 24 hours for my customers in the US and, after another day or so, the codes were also functioning in Europe.
So I guess the simple answer to my issue is "wait a little longer".
I have a HTML page with a Download app button. When clicked by an iOS user, it redirect the users to the App Store via itms-services. The link I used here is:
window.location.replace("itms-apps://itunes.apple.com/app/id578505616");
It looks like so on a mobile browser:
Facebook/Pinterest has an in-app browser which asks for the user's consent before redirect the user out of their app in the form of an Alert box with Cancel or Open app, which Open app opens the external link. It looks like this:
It looks like this with the Alert box:
Assuming the user is using an iOS device. The expected behavior here is when the Open app button is clicked, the user gets redirected to the App Store app. However, we are seeing about a 10 seconds delay before the actual redirection happens.
See videos below:
https://www.youtube.com/watch?v=_dgh7v-IsK8
https://www.youtube.com/watch?v=_LFHeRnBFgg
https://www.youtube.com/watch?v=82Y-kj-pMyw
Notes:
I can't seem to reproduce this at all times. It is only reproducible sometimes. Sorry!
Once a device is delayed for the first time, all subsequent links to AppStores will be fast, until roughly 1 day late. Rebooting the phone and/or clearing the browser cache and/or reinstall Facebook/Pinterest does not help reproducing this.
I tried to replace the itms-apps:// link with https://itunes.apple.com/us/app/trusper-tips-tutorials-how/id578505616?mt=8, but we were still experiencing the delay from time to time.
The delay seems to be exactly 10 seconds.
Why does this delay occur? This seems like a bad user experience.
My current theory is that the problem is on the Apple side. The reason being, once the Open app button is clicked, it is out of the hand of our website, as well as Facebook/Pinterest app. I presume, once the button is clicked, iOS is handling the actual context switch from one app to another. Therefore, it suggests that either the system call actually opening the URL is hanging, or the system call opening the App Store app is?? However, I haven't been able to prove either one to be true or false. Does anyone have a better explanation?
[Edit 04/02/2015]
I can confirm this problem still exists as of today on my phone (iPhone 5S w/ iOS 8.2).
I did some further research and found this article which I think is suggesting that this is a iOS system-related bug: OpenUrl freezes app for over 10 seconds
As there is no proper documentation on how it works, it is hard to pinpoint the cause of it.
Let me advance a theory.
Opening an app from browser causes a context switch; indeed from browser to App Store. So for the very first time it'd cost some time, while in subsequent times it will open faster as it will get opened from cache.
If you consider AppStore uses Keep-alive connection between iOS AppStore in device and iOS AppStore Server for the first time socket opening in server would seem higher than the subsequent times as subsequent request would reuse the same connection.
If the app is removed from the cache then it'd again take some time for the app to open and there would be a little network delay as the app would have lost the cookie for keep-alive connection then the app would have to endure the socketing opening cost.
There are also other factors like Safari hanging, resulting in some delay. You can read how Safari can be messed up here.
iOS doesn't have garbage collection, only things like ARC (Automatic Reference Counting). Each has its own advantages and drawbacks. Sometimes these drawbacks can surface and cause some problem; nothing is to be ruled out. For example a memory leak or app-crash might leave dangling pointers.
Technically, using itms-apps should give a little advantage over plain iTunes url because itms-apps should narrow down the search; itms-apps mean iTunes Music Store-apps.
A plain iTunes URL may be a Book (iBook), Music (iTunes), App (Appstore), etc ... so iOS might have to decide which app to launch.
I hope this helps.
I have been using my app during the day with no issues but I am now getting the following error on all requests I make to Parse to get objects:
2014-09-03 20:24:21.913 App[3407:332f] Error: Failed to initialize mongo connection (Code: 159, Version: 1.2.20)
Has anyone else experienced this and if so know the reason behind the message.
Thanks in advance.
EDIT:
Parse is down once again (no surprise) Here is the link to the new bug if you are having the same problem of mongo DB going down. The twitter and status website should be the same. Hopefully they fix this sooner rather than later.......
https://developers.facebook.com/bugs/665440236886829/
I am having the same problem and posted on the developers website you can follow it here.
https://developers.facebook.com/bugs/300758356778621/
Edit: They are experience a lot of different problems it sounds like right now. Facebook was down for awhile but is now up. They are still working on parse errors and crashes according to what the developer left on the link above.
So it is coming up slowly but people are still experiencing errors on top of following the bug at the link above here is there twitter account.
https://twitter.com/ParseStatus
Also their status website.
http://status.parse.com/incidents/m9k6y5qbz2dk
Should be up shortly (hopefully).
I have a simple Windows Phone App (7.1) that uses the LiveSDK and simply asks the user to sign in, grant access, and then is supposed to get their name and display it on the screen. Once I sign in, I get the following error:
A first chance exception of type 'System.NotSupportedException' occurred in System.Windows.dll
I have the correct Client ID, and have registered this as a Mobile app.
Anyone know what's happening here?
Re: the Redirect URL, i just left it blank since this is just a mobile app- and didn't specify one while setting up the Client ID.
Thanks!
You know I just ran into this same issue and it was confusing me for a bit. Then two things hit me.
It's a first chance exception
It's caught and handled by the Live SDK
I was too busy researching the error to try to actually continue through it :) Anyway it works fine if you let it continue.
I've got an app I'm ready to submit to Apple except for testing Game Center integration with their servers. That's where I've hit the following snag.
I've installed the app on my device, which is plugged into my laptop, and running the app in debug mode from XCode. When submitting an achievement or high score using GKAchievement or GKScore, I have been getting nothing but GKErrorCommunicationsFailure errors sent to the completion handler all day today (my first day trying). The app logs in to Game Center successfully and quickly, and the device can get on the internet with no difficulty for web sites (including Apple's), but these errors are all I can get out of the call to score/achievement-submission routines.
(The good news is that I've therefore thoroughly tested my handling of such an error! :) But now I'd like to see some submissions succeed!)
Any idea what might be causing this, or is the error actually correct, and I just picked the coincidentally worst network day to try this out?
I found out the problem, and so am answering my own question:
The GKErrorCommunicationsFailure is an umbrella for any number of different errors you might get from communicating with the server. It does not mean only a connection problem, for example.
In my case, it was that I had slightly different names for achievements/leaderboards in my code than on iTunes Connect (spaces in the code, no spaces on iTunes Connect). Thus the error was really trying to indicate that there was no such achievement/leaderboard to post.