gcm doesnt work with renameManifestPackage tag

What steps will reproduce the problem?
1. Create a project with using gcm (ex. c2dm);
2. Try to compile it with maven for different packages using 
renameManifestPackage;
3. Update manifest permissions by hands to prevent crash for different package 
name;

What is the expected output?
GCM service works correctly;

What do you see instead?
GCM couldnt register;

What version of maven-android-plugin are you using?
3.5.3

What are the complete output lines of "mvn -version" on your machine?

Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-oracle/jre
Default locale: ru_RU, platform encoding: UTF-8
OS name: "linux", version: "3.2.0-40-generic-pae", arch: "i386", family: "unix"

Please provide any additional information below.

Trying to build android project with gcm for different customers. If I build it 
with defauilt package "com.my.project" - gcm works correct.

When I try to build it for custom package, gcm doesnt work. To change package I 
use 
renameManifestPackage tag:

<renameManifestPackage>com.my.project.custom</renameManifestPackage>
Logcat:

04-18 16:37:53.834: DEBUG/GCMRegistrar(20891): resetting backoff for 
com.my.project.custom
04-18 16:37:53.854: VERBOSE/GCMRegistrar(20891): Registering app 
com.my.project.custom of senders xxxxxxxxxxxx
04-18 16:37:54.184: VERBOSE/GCMBroadcastReceiver(20891): onReceive: 
com.google.android.c2dm.intent.REGISTRATION
04-18 16:37:54.184: VERBOSE/GCMBroadcastReceiver(20891): GCM IntentService 
class: com.my.project.custom.GCMIntentService
04-18 16:37:54.194: VERBOSE/GCMBaseIntentService(20891): Acquiring wakelock

after Acquiring wakelock gcm stucked

Original issue reported on code.google.com by voz...@gmail.com on 18 Apr 2013 at 12:49

GunaSekharM / maven-android-plugin

gcm doesnt work with renameManifestPackage tag #369