[Mono-bugs] [Bug 641911] New: Debugger Fails to Attach Without Error When AndroidManifest Contains Incorrect Activity Name

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=641911

https://bugzilla.novell.com/show_bug.cgi?id=641911#c0


           Summary: Debugger Fails to Attach Without Error When
                    AndroidManifest Contains Incorrect Activity Name
    Classification: Mono
           Product: MonoDroid
           Version: unspecified
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Tools
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: pdbarnett at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Beta-Customer
           Blocker: No


Description of Problem:

When AndroidManifest.xml defines an activity whose name doesn't exactly match
the actual Activity class, the debugger deploys the application to the emulator
but then silently exits without launching the activity.


Steps to reproduce the problem:
1. Create a new blank MonoDroid project
2. Verify that you can run and attach the debugger (F5)
3. Edit AndroidManifest.xml
4. In the "application" node, add a child node similar to the following:

<activity android:name=".Activity1" android:label="@string/app_name">
      <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
      </intent-filter>
    </activity>

5.  Run and attached the debugger (F5)
6.  Observe that the project compiles and is deployed but then the debugger
simply exits and the application does not actually start.  No error is
displayed.

Actual Results:
Silent exit of the debugger after application deployment.

Expected Results:
Some type of error, at least a generic error though ideally something a little
more descriptive (e.g., "Unable to start Activity <name>.  Check your
manifest.")

How often does this happen? 
100%

Additional Information:
The scenario in which I hit this was porting an existing Eclipse project --
there manifest has ".MyActivity" whereas the actual class is "MyActivity". 
This works in Eclipse but fails in MonoDroid.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.