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中更改它。