Android 模拟器上的 fbconnect api (Java)
你好，我对 eclipse 和 android 模拟器很陌生。
我正在尝试在我的应用程序中连接到 Facebook。我已经下载并安装了所有正确的 SDK 和 fbconnect API，并使用 http:// www.mobisoftinfotech.com/blog/android/845/ 我已经成功导入和调试该项目。我已经处理了所有构建路径错误等等...
我现在遇到的问题是，当我运行 android 项目时，模拟器会加载并出现，但我收到以下消息“应用程序消息传递（处理中） com.android.mms) 没有响应”。
然后我尝试从 Android 模拟器运行它，并收到以下错误消息“应用程序 FB 连接（进程测试。One）已意外停止，请重试”。 我还尝试在各种 Android 版本（从版本 1.6 到 2.2）上运行该应用程序，但仍然没有成功！
关于如何解决这个问题的任何建议都会非常有帮助，因为我没有想法。
谢谢。
Hi there I am quite new to eclipse and the android emulator.
I am trying to connect to facebook in my app. I have downloaded and installed all the correct SDK's and the fbconnect API and using the tutorial from http://www.mobisoftinfotech.com/blog/android/845/ i have managaed to import and debug the project. I've dealt with all the build path errors and so on...
the problem the I am having now is that when I run the android project, the emulator loads and comes up but i get the following message "Application messaging (in process com.android.mms) is not responding".
i then tried to run it from the android emulator and i get the following error message " the application FB connect (process test.One) has stopped unexpectedly please try again".
i have also tried running the app on various android versions, from version 1.6 to 2.2 and still no luck!
Any suggestions as to how to fix this problem will be very helpful as i am all out of ideas.
thank you.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
嘿我明白了！ :) 哈哈，
基本上在 LogCat 工具的帮助下，我经历了所有出现的错误，并意识到我的项目中有 2 个 AndroidManifest XML 文件（由于持续导入），其中一个 Manifest 文件有一个不正确的包路径，所以我只是删除它并使用另一个:)这工作正常，并且模拟器第一次没有显示任何“强制关闭错误”！
希望这可以帮助任何犯同样错误的人（尽管这是一个相当金发的错误，但我们都生活和学习）。哈哈，
感谢所有男孩和女孩的意见。
hey I figured it out!! :) lol
well basically with the help of the LogCat tool I went through all the errrors that were coming up and realised that I had 2 AndroidManifest XML files sitting in my project (due to continuous importing), and one of those Manifest files had an incorrect package path, so I just deleted it and used the other :) this worked fine and for the first time ever the emulator did NOT show any "force to close errors"!
hope this helps anyone who makes the same mistake (even though it was a quite a blonde one, but we all live and learn). lol
thanks for all the input guys and girls.