Hordes of excited Google+ users trying to get the new v4.0 update of their favorite Android app were puzzled this morning when their devices running Ice Cream Sandwich and Jelly Bean were suddenly listed as incompatible. Numerous "WAT?!"s were exclaimed and heart attacks had, but don't worry, Google isn't canning Google+.

As you can see, the reason your devices are incompatible is simple - the Google+ team set the app compatibility to just Froyo and Gingerbread. As we suspected, it's just a temporary glitch - a Google+ engineer and Vic Gundotra already confirmed that the company is aware of the problem caused by a faulty manifest and is working on a fix:

Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

Thanks for the link. Just tried it and it crashes. Looks like I was wrong in this case.

http://www.twitter.com/joshuaworth Joshua Worth

Thank my lucky stars!

maestro PL

D'oh (in Homer Simpson's voice)

Chahk Noir

Somebody must've typed in "4.3" forgetting that they didn't announce it at the I/O.

omegavesko

You put the API level in the manifest, not the Android version. So you don't actually get to type 2.2, 4.3 etc. anywhere.

Plus, it's restricted to 2.2 and 2.3, nothing to do with 4.3.

Chahk Noir

I know, my way makes the joke funnier.

http://twitter.com/Jug6ernaut William

I wonder if this has to do with testing the new compatibility libraries announced at IO. Forcing compatability down to do testing and don't switching it back up for production.

Leonid Podolny

This is very typical. People are so used to Google killing off services that they have grown to love, that nobody actually doubts that Google can kill off the feature they have just announced a whole bunch of updates.

If you look further down the list you see "Logitech Revue 1" my guess is that they have 2 of the originals and just named them 1 and 2 to make them distinguishable.

http://www.androidpolice.com/ Artem Russakovskii

Yeah, I got two. Neither of which are used anymore because they're giant piles of steaming feces.

http://www.facebook.com/archercc Ryan Stewart

Sheeeet, I love mine. Its slow and laggy but I use the hell out of it. I wish one of the newer GTV boxes integrated harmony. I love the radio controlled central remote system that can use my phones.

http://www.androidpolice.com/ Artem Russakovskii

I would have kept mine hooked up, but both of them exhibit this issue where after a few days/weeks of being powered on, the sound starts breaking up constantly, and only a reboot fixes it. In the end, I got sick of this and unplugged them.

http://www.facebook.com/archercc Ryan Stewart

That sucks. Mine dont do that. I get occasionally when I turn it on the sound is silent but all i have to do is change a channel and it comes, Im guessing its the inbound HD connection. But that is like once every 2-3 months.

I want to upgrade to something with a bit more power but everyone else uses these crap little IR emitters while the revue has beastly ones that seem agnostic to the location of the Revue in the room.

Does Google TV support Hangouts yet? I want that stat, just ot be able to plug in a webcam and have hangouts on my massive TV without having to hook my tower up and run wires and such.

I looked and it looks like all but the ASUS(?) have blasters attached to the box. The only concern is they look to be those dinky little ones instead of the big ones on the Revue. I guess the little ones would work for hte stuff in the cabinet but probably arent powerful enough to get the sound system going.

http://www.mikestenger.com/ Mike Stenger

Darn. Average users will just have to wait a little longer to be confused with Hangouts now being alongside Messenger.

http://www.maverickcreative.ca/ Joshua Richards

Taking a mighty long time to fix that manifest file.

omegavesko

You'd think Google would be able to work around the Play Store update lag.

Matt

Well they still likely have to distribute it across servers. It's not like Google can make the dump trucks move the packets faster across that series of tubes.

Nah, that's not why it didn't work. The apk installed OK, but there were ClassCastExceptions. It really was compiled for 2.2-2.3 after all, as indicated by the Varies with device wording on the fixed listing.

Jeff Badger

As long as Ron can still do his APK teardown, I'm willing to wait.

Julio Lagara

No wonder I was finding it weird that I hadn't received the update message on my Play Store.

Mike Adams

First hangouts, now this.. Looks like they need to do better QA on their manifests.

http://www.facebook.com/archercc Ryan Stewart

Vic better put in some quality control. That is a pretty big cock up on some very small code.

Nasko Hristov

Ok, mine updated on mya A510 and Gnex, however in the site still shows 2.2-2.3.7

http://www.androidpolice.com/ Artem Russakovskii

All good now.

http://www.facebook.com/profile.php?id=1230008633 Jens Törnblad

I am disappointed with the update.
Still doesn't allow me to swipe in the sidebar and it doesn't feature the new design guidelines.
The bar in the bottom has a new (completely black) color and a white line underneath it to seperate it from the navigation bar. Looks really ugly.
Messenger is still there.

Krzysztof Radzikowski

fixed
This app is compatible with all of your devices.

Wylan

Man, they are slacking the last week. Forgot to check the boxes for ICS and JB on g+ and the Kickoff video for IO was/is desktop only. Come on Google, pull your heads out...