This morning I had 5 apps come up for update. Two of them updated fine. The last three stalled about mid-way through and then showed the attention required message. When I tap the the message I get "There is a problem completing your request. Try again later. Error Code: 8103010d
All three apps are demos, but the two that completed were as well. Googling the error code did not bring up anything useful.
Probably because mango is in beta and the apps haven't been fully updated to mango
Sent from my T9295 using XDA Windows Phone 7 App
jklier said:
This morning I had 5 apps come up for update. Two of them updated fine. The last three stalled about mid-way through and then showed the attention required message. When I tap the the message I get "There is a problem completing your request. Try again later. Error Code: 8103010d
All three apps are demos, but the two that completed were as well. Googling the error code did not bring up anything useful.
Click to expand...
Click to collapse
If had the same error yesterday with PES2011 (full version) and today with Turn by Turn Navigation. I managed to get the latest PES2011 by uninstalling and then downloading the complete new version again. Doesn't seem to work with TBT, since it's grayed out for some reason.
@nalgrim
It's most definitely an issue with the mango beta. But I'm very certain it's not by far related to apps not being updated for mango. None of the apps currently available on the marketplace is.
Turn by Turn was one of mine as well. I figured it had something to do for Mango but I'm just checking to see if there's a work around. Since updating to Mango I've had dozens of updates with no issues.
Not a big deal. I'm still enjoying Mango even as a beta version.
I found that when I tried updating certain apps over my data connection I had this (or at least I think it was this) issue. Updating over wifi seemed to fix it though.
Casey
Casey_boy said:
I found that when I tried updating certain apps over my data connection I had this (or at least I think it was this) issue. Updating over wifi seemed to fix it though.
Casey
Click to expand...
Click to collapse
I tried both, data and WiFi. None of them worked for me. At least not with TBT.
Same here. WIFI didn't make a difference.
I noticed that it's not the download that fails, but the installation. Download in Mango is always completed when the 50% mark is reached. After that the installation process starts. That's where the error occurs.
dkp1977 said:
I noticed that it's not the download that fails, but the installation. Download in Mango is always completed when the 50% mark is reached. After that the installation process starts. That's where the error occurs.
Click to expand...
Click to collapse
Someone who has figured out what to do? I got this problem today with hTC hub update.
I know this is an old thread but, I wanted to put a post here for people with this issue. I had a demo installed and I tried to buy the app and I got the 8103010d error(this is with a current version 8107 not just mango). I uninstalled the demo with the same error.
I went online and found a sideload version(a hacked version) of the app and installed it. Then I uninstalled it. I attempted to reinstall from the marketplace and it installed fine.
As I dont promote pirating software, it fixed my issue here, just make sure you delete the pirated software after attempting this.
DavidinCT said:
I know this is an old thread but, I wanted to put a post here for people with this issue. I had a demo installed and I tried to buy the app and I got the 8103010d error(this is with a current version 8107 not just mango). I uninstalled the demo with the same error.
I went online and found a sideload version(a hacked version) of the app and installed it. Then I uninstalled it. I attempted to reinstall from the marketplace and it installed fine.
As I dont promote pirating software, it fixed my issue here, just make sure you delete the pirated software after attempting this.
Click to expand...
Click to collapse
Well I think simply uninstalling the demo or whatever the old app is and then installing the new one should do the work. It did for me.
Hi guys,
Newbie here, just got my Arc last week.
I have problems with my games (at least for now), I downloaded apks via google search instead of buying them from the market. I installed them and when I tried to run the game, there's the initial message saying additional data should be installed or downloaded to the phone.
However, upon tapping yes I'm getting this error message over and over again: A problem occured and the download could not be completed succesfully. Do you want to restart the download?
Also, the pre-installed game Let's Golf has this annoying issues.
I have a stable wifi connection. What seems to be the problem?
EDIT: Already figured it out. Our IT Personnel blocked all file-sharing sites in our connection without telling us.
@lawgone
We don't discuss warez here over at XDA. I don't think the other members would appreciate what you do.
Moreover, you run the risk of installing malware on your phone. Be wary of what you install.
Cheers!
Don't know what I did...or when even...but I can no longer sideload apps to my Focus. The App Deployer gives an error stating it cannot connect to the device...make sure it is fully booted and plugged in to the PC. Problem is that it is. I have verified that it is fully unlocked...I can use sideloaded apps already on the phone and used Samsung Registry to go and verify the keys. I have been running the RTM and updated it today. I also updated my wifes LG Quantum today...she was still on NoDo. After updating her phone I tried sideloading and it said she was not unlocked so I went in and unlocked her phone and then it sideloaded as expected.
So long story there, does anybody have any ideas on what might be the issue.
So TIFU by losing my iPhone. And i ****ed up even more by updating my backup spare Galaxy Nexus from 4.1 to 5.1 directly without clearing data or doing any background study. Simply went to update and there the plight started. I was connected to Wifi but my Play Store wasnt working. Was saying no network or something on those lines with the "Retry" button. So i thought uninstalling Playstore and reinstalling would be a good idea. NOT. It wasnt even close to the right step, now everything is crashing and I dont know what I should be doing next. If someone can tell me the best way to get to a new installation of 5.1.1 on this device and root it, it would be great. I right now have CWM recovery 6.3.x(?) installed. I wish to at least be able to install apps from the appstore and update the 2 year old applications. Please help.
Hi
I was on Android 12 and signed in to the beta program 10 days ago.
I've noticed that APKs that were fine on Android 12 are not working anymore on Android 13 Beta.
APKs are crashing at opening.
I thought that may have been an issue related to the beta version of Android but couple of days ago Android 13 stable rolled out (I've signed out from the beta) but those apps are still not working.
I've found older APKs for a couple of apps and one works and one not.
How can I solve this without a factory reset?
Thank you in advance
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
skymera said:
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
Click to expand...
Click to collapse
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Lughnasadh said:
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Click to expand...
Click to collapse
Wasn't aware of this, thanks!
I don't have any issues with manually installed apks...
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Waiting till the weekend to update, but what APKs are giving the error?
skymera said:
Wasn't aware of this, thanks!
Click to expand...
Click to collapse
Can't find this
Jeff_N said:
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Click to expand...
Click to collapse
Do those apps need Accessibility and/or Notification Access permissions? If not, then I don't think the 3 dot menu needs to be there as it is only for those specific permissions (or whatever other permissions Google might add to the list in the future).
For example, I have Adaway installed but it doesn't have the 3 dot menu because it doesn't need either of those permissions. The same for App Manager.
I am really confused with this new "session-based install" security.
What are "session-based install" and "non-session-based install"
Play store app install --------- surly "session-based install" 100%.
3rd-party store install --------- is said also to be "session-based install".
Firefox download an apk --------- is said to be "non-session-based install",
But how the firefox different from a 3rd-party store????? a system white list something?
safetynet, selinux, forcing many settings, anti-rollback, non-store app restrictions.........
I enjoyed so much that google throws sht tons of troubles to billions of advanced users, to fight an enemy that may not even exist.
(how many people have their phone bootloader secretly unlocked remotely by a hacker and installed root malware, unknowingly?)
Gives a warning is good eg. bootloader locked warning is great IMO. But force the hands and keep finding ways to screw the advanced users as hard as they can, to get the "everything is under my control" status is the wrong path.
I read the news that malware devs have already found a way to bypass this restriction.
In the end, like many others, It achieved nothing, except giving trouble to advanced users and devs.
A global bypass must be also on the way, especially from China. Millions like 90% of APPs are not store-based in China since the google ban, and people are used to download apk from every companies' websites as we do on Windows PC.
somethingsomethingroot said:
Waiting till the weekend to update, but what APKs are giving the error?
Click to expand...
Click to collapse
3 APKs from the company I'm working for (not on PlayStore) 2 sideloaded apps, and a LADB signed sideloaded APK
For example you cut and CC cleaner keeps crashing all the time.
Same here. Almost every app not from Play Store keeps closing right on tap to start them.
Tried to sideload them per USB with full rights. Same.
My company apps that didn't come from the play store are opening without a problem
Thats Vers Strange, indeed.
Every sideloaded App, modded or Not does Not work
Thought it was me...this is bs!
What's the next step...start posting logs I assume?
It's not EVERY sideload for me but about 1 in 3 I'd say.
btw...I got an 'install failed' trying to install/flash the viper4android mod not realizing how old it was...now I'm seeing lotsa audio/sound related crap in logcat reader. If I AM 'currupt' somehow, will just a rom re-flash fix a magisk issue or do I need a full wipe?
Tia for any guidance offered!
Zaxx32 said:
Thought it was me...this is bs!
Click to expand...
Click to collapse
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
salamala893 said:
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
Click to expand...
Click to collapse
12 won't work right on the 13 bootloader, and you can't downgrade the bootloader.
When I initially tested flashing only the 13 bootloader on my Pixel 6 Pro, while still running Android 12, it booted fine, I unlocked the phone, and all looked normal. But I didn't launch apps, especially Chrome, YouTube, and plenty of other things. If I had, I would have noticed problems that others have had since then. It was since found that certain/many kinds of apps will not work right running on Android 12 when you have the 13 bootloader installed.
I know this above is not what this thread is discussing, but since you mentioned it, I just wanted to point out that if you're on any Pixel 6/Pro/a with Android 13's bootloader flashed, you won't be able to use stock Android 12 on it. You'll be able to flash everything but the bootloader, boot it up, and unlock it, but before long you would discover problems that you wouldn't be able to work around and would effectively make your phone unuseable for many things that we take for granted.
By the way, hopefully you have the 13 bootloader flashed to both slots. Having the 13 bootloader on only one slot is a little dangerous.
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img
Guys, but are you talking of sideloaded apps, or apps installed as apk?
gpvecchi said:
Guys, but are you talking of sideloaded apps, or apps installed as apk?
Click to expand...
Click to collapse
Apks