Skip to main content

Stalled iOS application updates

For whatever reason, iOS has a tendency to suffer from stalled application updates when updating from the device.  This behavior has been observed numerous times since the iOS 6 update was released.  The observations have come by-way-of two 4th generation iPod touches with strong Wi-Fi connectivity.  The issue is independent of software titles.

A few Internet searches have yielded some information about store problems, but the issues range from problems with song downloads to 5-year-old forum posts.  The issue at hand here is straight software updates from the “Updates” tab of the App Store application.

Fortunately, the apparent solution is simple, and is likely by design.  It’s just puzzling why no-one seems to be posting the fix.  That is, unless it’s so simple that it goes without saying.  At-any-rate, here it is.  Browse the device to the application’s icon and just touch it as though launching the application.  The label on the application should indicate that the update is continuing and the stalled progress bar on the icon should start moving again.

It’s convenient for Apple to have built-in a mechanism by which an update will gracefully pause itself if network availability goes away.  It’s inconvenient of Apple to not have built-in a way for the App Store to know when network availability has been restored and to resume stalled downloads.  The curious part is that while there are “paused” updates, other applications are able to be updated “willy nilly.”  Yet, the paused applications stay paused indefinitely.  This, combined with the fact that good Wi-Fi connectivity was available the whole time during these experiences leads to the conclusion that this is simply a bug with the App Store.  Fortunately, the workaround described here works pretty well—so far.
Labels:

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more