Known Issues

JUnit and Eclipse/ADT

• If you are developing in Eclipse/ADT and want to add JUnit test classes, you can do so. However, you need to set up a custom JUnit configuration before your tests will run properly. For detailed information about how to set up the JUnit configuration, see the troubleshooting topic Running a Junit test class in Eclipse.


• It is not possible to send MMS messages between emulator instances.

• In some cases, you may encounter problems when using the browser on an emulator started with the command-line option -http-proxy.

• On the OSX platform, if you manually remove the ~/.android directory using rm -rf ~/.android, then try to run the emulator, it crashes. This happens because the emulator fails to create a new .android directory before attempting to create the child SDK1.0 directory. To work around this issue, manually create a new .android directory using mkdir ~/.android, then run the emulator. The emulator creates the SDK1.0 directory and starts normally.

• We regret to inform developers that Android 1.1 will not include support for ARCNet network interfaces.

• The final set of Intent patterns honored by Android 1.0 has not yet been fully documented. Documentation will be provided in future releases.

• In ADT Editor, you can add at most ten new resource values at a time, in a given res/values/*.xml, using the form in the Android Resources pane. If you add more than ten, the Android Resources pane will not display the attributes fields for the additional resource entries. To work around this problem, you can close the file in the editor and open it again, or you can edit the resource entries in the XML text mode.

• The emulator's battery-control commands (power <option>) are not working in this release.

The USB driver files are located in the <SDK>/usb driver directory. For details and installation instructions, see Setting Up a Device for Development.

Resolved Issues, Changes Emulator

0 0

Post a comment