Android项目重命名 - 现在不会启动

Question

成功测试后，我尝试将我的项目/软件包从'test ...'重命名为更相关的项目。我尽可能使用了各种Eclipse重构助手。所有的源文件似乎都有正确的软件包在顶部，清单似乎有正确的软件包名称等。我执行了“清理”。

一切似乎都很好。唯一的问题是它不会启动 - 甚至没有进入onCreate（）处理程序的活动。它在AvtivityThread.performLaunchActivity（ActivityThread $ ActivityRecord，意图）第2417行崩溃。

很明显，它仍然有旧名称，但我找不到它。

任何建议在哪里看/做什么？

按照要求：登录猫（控制台没有）：

07-14 07:00:04.149: D/AndroidRuntime(347): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<<br> 
07-14 07:00:04.149: D/AndroidRuntime(347): CheckJNI is ON<br> 
07-14 07:00:04.389: D/AndroidRuntime(347): --- registering native functions ---<br> 
07-14 07:00:04.830: D/ddm-heap(347): Got feature list request<br> 
07-14 07:00:05.239: D/AndroidRuntime(347): Shutting down VM<br> 
07-14 07:00:05.250: D/dalvikvm(347): DestroyJavaVM waiting for non-daemon threads to exit<br> 
07-14 07:00:05.250: D/dalvikvm(347): DestroyJavaVM shutting VM down<br> 
07-14 07:00:05.250: D/dalvikvm(347): HeapWorker thread shutting down<br> 
07-14 07:00:05.259: D/dalvikvm(347): HeapWorker thread has shut down<br> 
07-14 07:00:05.259: D/jdwp(347): JDWP shutting down net...<br> 
07-14 07:00:05.269: I/dalvikvm(347): Debugger has detached; object registry had 1 entries<br> 
07-14 07:00:05.279: D/dalvikvm(347): VM cleaning up<br> 
07-14 07:00:05.291: E/AndroidRuntime(347): ERROR: thread attach failed<br> 
07-14 07:00:05.309: D/dalvikvm(347): LinearAlloc 0x0 used 629532 of 5242880 (12%)<br> 
07-14 07:00:05.801: D/AndroidRuntime(355): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<<br> 
07-14 07:00:05.809: D/AndroidRuntime(355): CheckJNI is ON<br> 
07-14 07:00:06.049: D/AndroidRuntime(355): --- registering native functions ---<br> 
07-14 07:00:06.490: D/ddm-heap(355): Got feature list request<br> 
07-14 07:00:06.910: D/ActivityManager(52): Uninstalling process uk.co.nightshadearts.golfcaddy<br> 
07-14 07:00:06.910: I/ActivityManager(52): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=uk.co.nightshadearts.golfcaddy/uk.co.nightshadearts.golfcaddy }<br> 
07-14 07:00:06.969: D/AndroidRuntime(355): Shutting down VM<br> 
07-14 07:00:06.969: D/dalvikvm(355): DestroyJavaVM waiting for non-daemon threads to exit<br> 

07-14 07:00:07.009: E/AndroidRuntime(355): ERROR: thread attach failed<br> 
07-14 07:00:07.009: D/dalvikvm(355): DestroyJavaVM shutting VM down<br> 
07-14 07:00:07.009: D/dalvikvm(355): HeapWorker thread shutting down<br> 
07-14 07:00:07.019: D/dalvikvm(355): HeapWorker thread has shut down<br> 
07-14 07:00:07.019: D/jdwp(355): JDWP shutting down net...<br> 
07-14 07:00:07.019: I/dalvikvm(355): Debugger has detached; object registry had 1 entries<br> 
07-14 07:00:07.051: D/dalvikvm(355): VM cleaning up<br> 
07-14 07:00:07.070: D/dalvikvm(355): LinearAlloc 0x0 used 639500 of 5242880 (12%)<br> 
07-14 07:00:07.160: I/ActivityManager(52): Start proc uk.co.nightshadearts.golfcaddy for activity uk.co.nightshadearts.golfcaddy/uk.co.nightshadearts.golfcaddy: pid=362 uid=10031 gids={1015}<br> 
07-14 07:00:07.309: D/ddm-heap(362): Got feature list request<br> 
07-14 07:00:07.460: W/ActivityThread(362): Application uk.co.nightshadearts.golfcaddy is waiting for the debugger on port 8100...<br> 
07-14 07:00:07.489: I/System.out(362): Sending WAIT chunk<br> 
07-14 07:00:07.510: I/dalvikvm(362): Debugger is active<br> 
07-14 07:00:07.750: I/System.out(362): Debugger has connected<br> 
07-14 07:00:07.750: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:07.951: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:08.150: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:08.350: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:08.559: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:08.759: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:08.960: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:09.187: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:09.397: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:09.609: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:09.827: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:10.039: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:10.263: I/System.out(362): waiting for debugger to settle...<br> 
07-14 07:00:10.479: I/System.out(362): debugger has settled (1449)<br> 
07-14 07:00:10.681: E/gralloc(52): [unregister] handle 0x3fa718 still locked (state=40000001)<br> 
07-14 07:00:17.029: W/ActivityManager(52): Launch timeout has expired, giving up wake lock!<br> 
07-14 07:00:17.391: W/ActivityManager(52): Activity idle timeout for HistoryRecord{44f00a48 uk.co.nightshadearts.golfcaddy/uk.co.nightshadearts.golfcaddy}<br> 

电话：

GolfCaddy [Android Application]  
DalvikVM[localhost:8610]  
    Thread [<3> main] (Suspended (exception RuntimeException))  
     ActivityThread.performLaunchActivity(ActivityThread$ActivityRecord, Intent) line: 2417  
     ActivityThread.handleLaunchActivity(ActivityThread$ActivityRecord, Intent) line: 2512  
     ActivityThread.access$2200(ActivityThread, ActivityThread$ActivityRecord, Intent) line: 119  
     ActivityThread$H.handleMessage(Message) line: 1863  
     ActivityThread$H(Handler).dispatchMessage(Message) line: 99  
     Looper.loop() line: 123  
     ActivityThread.main(String[]) line: 4363  
     Method.invokeNative(Object, Object[], Class, Class[], Class, int, boolean) line: not available [native method]  
     Method.invoke(Object, Object...) line: 521  
     ZygoteInit$MethodAndArgsCaller.run() line: 860  
     ZygoteInit.main(String[]) line: 618  
     NativeStart.main(String[]) line: not available [native method]  
    Thread [<13> Binder Thread #2] (Running)  
    Thread [<11> Binder Thread #1] (Running) 

答：

其实，我似乎已经解决了这个问题，但我不我真的知道我已经修好了什么。在app won't install after package rename

以下说明fromn alextsc我做了以下内容：

完全甩故障项目（已删除项目和文件树） - 幸好我有常识，有抄袭之前，我做了什么原。

在'workbench'下复制原件。

使用从现有源选项创建的方式添加了新项目（原始名称）。

让它恢复工作。

然后在项目中使用rt clk并选择Android Tools >>重命名应用程序包，然后让它执行所需的任何操作。

但是，在src下，程序包仍然有旧名称。使用Eclipse重构来更改为新名称。

似乎仍然有效。所有的src文件都有正确的包装。

重命名（一个）活动 - 仍然有效。之后，它只是更多的内部代码modifactions行XML应用程序名称。

结论：Android Tools >>重命名应用程序包做了一些事情，但我不知道是什么。道德：选择一个名字并在未来坚持下去。

Answer 1

清单中改变这个R.java之后将新包下创建再次，然后你必须在所有的活动中导入R改为包名称

<manifest xmlns:android="http://schemas.android.com/apk/res/android" 
    package="com.org.xxx" // your packagename here.. 
    > 
    </manifest> 

..

试试这个，它可能对你有帮助..

Answer 2

这是我做的。

在Eclipse项目的“src”文件夹中，您将拥有名为“com.test ...”的内容，将其重命名为新名称，然后单击确定。然后所有的文件应该自动更新。至少它对我来说非常合适。

请记住，您还必须在Android Manifest中更改它。