Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of cjp822@gmail.com designates
 209.85.214.175 as permitted sender)
MIME-Version: 1.0
From: Connor Pearson <cjp822@gmail.com>
Date: Fri, 13 Feb 2015 08:30:29 -0500
Message-ID: 
 <CAE82UFYCR8KKO1XXhKazdTYg3xMm_vBfp+HUc51WCvKRqQ00Xg@mail.gmail.com>
Subject: Thoughts on CB-7827
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=001a113d631eb2d274050ef83e21

--001a113d631eb2d274050ef83e21
Content-Type: text/plain; charset=UTF-8

Hi all,

I'm wondering what the status of CB-7827 is. It causes the APK and activity
name to be set to a hardcoded value. It's been open since October and has
more votes and watchers than any other Cordova bug.

According to the Android documentation (
http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html),
you should never change the android:name attribute. So developers working
on an already published app must perform a manual fix of several files
every time the android platform is added.

The root cause of the issue is Cordova now hardcodes the main activity name
as CordovaApp (or MainActivity). This was done to fix CB-6511. I have a
couple of ideas for fixing this bug without regressing CB-6511:

- Use the project name as the activity name then fall back to the hardcoded
name if the project name uses 16 bit characters.

- Allow the user to specify android-activityName in config.xml. Similar to
android-versionCode.

- Another option could be to combine the two, attempting to use
android-activityName first then falling back to the project name then
finally falling back the hardcoded name.

Do you think any of these ideas are worth pursuing? I'd be willing to work
on a pull request, but I want to make sure I'm going in the right direction.

Thanks,
Connor

--001a113d631eb2d274050ef83e21--