Background notifications writing 401 error to log.
I've tweeted back and forth a couple of times from my @OpenXiminez account, but I figure this forum will be more productive.
I'm migrating from Tweed, and at first, couldn't get any notifications to work. While I think I've got foreground notifications straightened out, I'm still getting nothing out of background. I've got a Verizon Pre Plus, just upgraded to WebOS version 1.4.5.1. Carbon version is 1.2.1. Unfortunately, I upgrade WebOS and installed Carbon at about the same time, so I can't tell if the problem is new with the OS upgrade. On top of that I normally run UberKernel and have a ton of patches installed. Oh, and I have two Twitter accounts. I'm nnot making this easy, am I? Despite all the customization, though, Carbon is the only app I'm having trouble with.
First, the foreground notifications seemed to start working when I changed the Timeline / Auto Refresh setting from "Disabled" to "Every 30 minutes". I had Notifications / Run Every set to "1 hour". I kept the cards open for both accounts all day, and got notifications periodically all day, too. Unfortunately, I've been too busy today to keep track of how often I was getting the notifications. Right now, however, I changed the Notifications / Run Every to 5 minutes, and I'm still waiting to see if it'll work.
Anyway, satisfied that foreground notifications are working, I switched to background notifications, every 5 minutes. Like I said above, I got no notifications, but then I fired up "Lumberjack", a system log viewer, and found that every 5 minutes (more or less), it was logging "Update error: 401" (thus the subject of the post). I've seen 401 errors mentioned elsewhere in the discussion boards, but not in any context like this.
I've been on wifi most of the day, but I've been on 3G for a big chunk of it, too.
I know I've gotten long-winded here, but I hope more detail will help, and I'm willing to debug this issue as far as I can. I've even thought about "doctoring" my phone, because of the potentially messed up OS upgrade, but I'm not quite at that point yet.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Moe on 22 May, 2011 07:10 AM
First, thank you very much for the detailed out write up and testing, this is highly appreciated.
We've a had a couple of users on Pre+ having the same issue, 401 Errors specially of this kind happens only when processing cycles change where the Timestamps that get posted to Twitter get messy causing Invalid Signatures for requests. Could you do one more thing to confirm where the issue exactly is? Could you revert back to Palm's default Kernel and see if the same error gets logged for BG Notifications? Thanks a million again for the report.
3 Posted by Ximinez on 22 May, 2011 06:12 PM
I'm happy to help. I know how useful a good write-up can be.
I've just finished doing the following:
- Reverted back to the default kernel - Rebooted - ...Waited... :) - Fired up Carbon for my default account. - Turned on background notifications. - Set "Run every" to 15 minutes. - Exited Carbon. - Restarted Carbon, and launched a card for my non-default account, just for good measure. - Closed both cards
I'll report back with my results when I have some.
Oh, and two more data points. Both accounts have the "Always use HTTPS" option set. One account is public, and one is private.
Support Staff 4 Posted by Moe on 23 May, 2011 12:06 AM
Thank you for that, I'll be waiting for the results, in the meantime it looks like I found another candidate for the issue which I'll confirm after your test results. Thank again.
5 Posted by Ximinez on 23 May, 2011 01:22 AM
These are the results after running for a while with background notifications turned on. I'm pretty sure the messages from 19:13 to 19:47 were from me triggering it manually. Either way, though, I didn't get any notifications.
[2011-05-22 19:09:31] (Carbon) Error: Update Error: 401 [2011-05-22 19:09:35] (Carbon) Error: Update Error: 401 [2011-05-22 19:09:45] (Carbon) Error: Update Error: 401 [2011-05-22 19:09:48] (Carbon) Error: Update Error: 401 [2011-05-22 19:13:01] (Carbon) Error: animateWithTimer: 52 [2011-05-22 19:13:16] (Carbon) Error: ^^^^ TimelineModel#detectGap [2011-05-22 19:13:16] (Carbon) Error: Count Condition: false [2011-05-22 19:13:16] (Carbon) Error: Time Difference Condition: true [2011-05-22 19:31:09] (Carbon) Error: ^^^^ TimelineModel#detectGap [2011-05-22 19:31:09] (Carbon) Error: Count Condition: false [2011-05-22 19:31:09] (Carbon) Error: Time Difference Condition: true [2011-05-22 19:31:10] (Carbon) Error: animateWithTimer: 52 [2011-05-22 19:31:18] (Carbon) Error: ^^^^ TimelineModel#detectGap [2011-05-22 19:31:18] (Carbon) Error: Count Condition: false [2011-05-22 19:31:18] (Carbon) Error: Time Difference Condition: true [2011-05-22 19:47:43] (Carbon) Error: Update Error: 401 [2011-05-22 19:47:44] (Carbon) Error: Update Error: 401 [2011-05-22 19:47:54] (Carbon) Error: Update Error: 401 [2011-05-22 19:47:55] (Carbon) Error: Update Error: 401
Funny thing is that now that I'm done with the test, I switched back to foreground notifications, and I'm not getting those either.
6 Posted by Ximinez on 23 May, 2011 01:32 AM
Oh, wow, that was ugly. Let's see if this is any better...
Support Staff 7 Posted by Moe on 23 May, 2011 04:16 AM
Thanks again for the logs, it's highly helpful, looks like I found where the source of the problem is, I'll test it and update this post and if confirmed I'll submit an update right away to fix this... Thanks again :)
8 Posted by Ximinez on 23 May, 2011 03:04 PM
Woo hoo!
Moe closed this discussion on 16 Aug, 2011 09:12 PM.