[ACK] BUG: "Update Now" / "Checking for Updates" (MAC OS X)

JT (alabama24)

I have "auto download updates" set to "no." Several thoughts about recent betas:

I am finding more and more often that I must type "update now" to check on updates. For example, I knew that beta 4 was available so I started up Logos and waited longer than I thought necessary for the update to be recognized. I clicked on the sync wheel to see if that would cause the update to be recognized... it wasn't, so I used the command.
The "checking for updates" command sometimes takes FOREVER. (Not shown in the logs below)
The "checking for updates" pop up will often remain indefinitely, even though updates have been found, downloaded, and indexed. (see screen shot)

5857.LogosLogs.20150608-201555.zip

Find more posts tagged with

Comments

Dave Hooton

I have "auto download updates" set to "no." Several thoughts about recent betas:

I am finding more and more often that I must type "update now" to check on updates. For example, I knew that beta 4 was available so I started up Logos and waited longer than I thought necessary for the update to be recognized.

The first statement is ambiguous as I always use "update now" (when Logos is running!). But I'm puzzled that there could be another situation that "forces" you to use it.

JT (alabama24)

https://community.logos.com/discussion/comment/734212#Comment_734212

The first statement is ambiguous as I always use "update now" (when Logos is running!). But I'm puzzled that there could be another situation that "forces" you to use it.

By "forces" me to use it I mean that L6 doesn't, within a couple of minutes, automatically recognize that there is an update and present it to me. If I want the update, I am "forced" to use the command. This behavior is different than before where updates were more quickly recognized and presented.

Andrew Batishko

In the current version of the application, the "update now" and "update resources" commands are not allowed to run at the same time as any other ongoing update-related activity. You can see the evidence of this in your log file if you search for "pending completion of". This can potentially keep the "Checking for updates..." toast visible for an extended period of time, as the "update check" waits for completion of other things.

From your log, it looks like the main window becomes visible at 19:49:21, and the first update check finishes at 19:50:59. Then the application update starts downloading at 19:51:05. The first update check is automatically triggered on application startup, and seems to be doing a full resource check, which is why it takes a while.

JT (alabama24)

https://community.logos.com/discussion/comment/734313#Comment_734313

From your log, it looks like the main window becomes visible at 19:49:21, and the first update check finishes at 19:50:59. Then the application update starts downloading at 19:51:05.

Are you saying that the log indicates the program opened at 19:49 and began downloading three minutes later? I'll keep a closer eye on it to see how long it takes from startup.

This can potentially keep the "Checking for updates..." toast visible for an extended period of time, as the "update check" waits for completion of other things.

...but the toast remained after the resources / application had already downloaded! Did I not understand you correctly?

John Fidel

https://community.logos.com/discussion/comment/734316#Comment_734316

I am with Alabama. The toast should disappear once a download is located. Same issue on a Mac.

JT (alabama24)

https://community.logos.com/discussion/comment/734375#Comment_734375

Same issue on a Mac.

We are both on mac. [:)]

Andrew Batishko

https://community.logos.com/discussion/comment/734316#Comment_734316

From your log, it looks like the main window becomes visible at 19:49:21, and the first update check finishes at 19:50:59. Then the application update starts downloading at 19:51:05.

Are you saying that the log indicates the program opened at 19:49 and began downloading three minutes later? I'll keep a closer eye on it to see how long it takes from startup.

1 minute and 44 seconds after the main window appeared, the update started downloading. It technically would have started 6 seconds sooner if you'd waited instead of using the "update now" command. [:P]

This can potentially keep the "Checking for updates..." toast visible for an extended period of time, as the "update check" waits for completion of other things.

...but the toast remained after the resources / application had already downloaded! Did I not understand you correctly?

Ah, I understand. I believe the toast not automatically closing is a long-standing behavior on the Mac. We've created a case for the problem.