entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://github.com/realm/realm-js/issues/491|blocks|key|6p7fr|text|你在android远程调试中遇到了一些已知的问题，但这些问题正在解决中。您可以在此处跟踪进度：https://github.com/realm/realm-js/issues/491|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|15b26^0|1B|18|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|L|G|@]|H|@$I|M|J|N|A|O]]|6|$]]|$A|K|C|-4|2|E|F|P|G|@]|H|@]|6|$]]]]

You're running into known issues w/ android remote debugging, but they're being worked on. You can track progress here: <a href="https://github.com/realm/realm-js/issues/491" rel="nofollow noreferrer">https://github.com/realm/realm-js/issues/491</a>

entityMap|blocks|key|3pr71|text|简单的解决方法是转到node_modules/realm/lib/browser/rpc.js并用let+url+=+'http://127.0.0.1:8083/'+%2B+command;替换第216行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|95uhe^0|A|11|1D|19|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@$A|I|B|J|C|D]|$A|K|B|L|C|D]]|E|@]|F|$]]|$2|G|4|-4|6|7|8|M|9|@]|E|@]|F|$]]]]

Easy fix is to goto <code>node_modules/realm/lib/browser/rpc.js</code> and replace line 216 with <code>let url = 'http://127.0.0.1:8083/' + command;</code>

entityMap|blocks|key|8dulq|text|当我使用react+native和realm数据库时，我遇到了这个问题。我认为您需要手动反向和转发端口以避免冲突port.When如果启用调试模式，请打开命令行并执行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|fbbon|+++`adb+reverse+tcp:8081+tcp:8081`
+++`adb+forward+tcp:8082+tcp:8082`|code-block|syntax|javascript|efodk|然后，您可以重新加载并进入调试模式。|2encq|干杯！|c0ge3^0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|N|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|O|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|P|9|@]|A|@]|B|$]]|$2|L|4|-4|6|7|8|Q|9|@]|A|@]|B|$]]]]

I've met this problem when I've used react native with realm database. I think you need manually port reverse and forward to avoid conflict port.When you enable debug mode, please open command line and follow below command:

<pre><code> `adb reverse tcp:8081 tcp:8081`
 `adb forward tcp:8082 tcp:8082`
</code></pre>

Then, you can reload and go into debug mode.

Cheer!

entityMap|blocks|key|1kpu1|text|如果@johnny的回答不起作用，当您键入命令时|type|unstyled|depth|inlineStyleRanges|entityRanges|data|645me|adb+reverse+tcp:8081+tcp:8081+adb+forward+tcp:8082+tcp:8082|offset|length|style|CODE|fbj5q|然后您会得到以下消息|apfnd|adb+server+is+out+of+date.++killing...
*+daemon+started+successfully+*|code-block|syntax|javascript|1eein|这意味着您在命令行中使用的adb命令与仿真器使用的adb工具是不同的。|5vu5k|您可以通过检查adb的位置来确认这一点(在这里，我在/usr/bin和/home中有两个不同的工具，这两个工具并不是后来验证的符号链接)|d2382|42:~/pathToMyApp$+whereis+adb
adb:+/usr/bin/adb+/home/42/Android/Sdk/platform-tools/adb+/usr/share/man/man1/adb.1.gz|7o3iv|我在两个工具上尝试了完整路径，我发现仿真器正在使用/home/中的adb工具...所以为了让它工作，我现在输入|4qdp1|/home/42/Android/Sdk/platform-tools/adb+reverse+tcp:8081+tcp:8081;
/home/42/Android/Sdk/platform-tools/adb+forward+tcp:8082+tcp:8082|65opc^0|0|0|T|U|T|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|10|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|11|9|@$E|12|F|13|G|H]|$E|14|F|15|G|H]]|A|@]|B|$]]|$2|I|4|J|6|7|8|16|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|17|9|@]|A|@]|B|$N|O]]|$2|P|4|Q|6|7|8|18|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|19|9|@]|A|@]|B|$]]|$2|T|4|U|6|M|8|1A|9|@]|A|@]|B|$N|O]]|$2|V|4|W|6|7|8|1B|9|@]|A|@]|B|$]]|$2|X|4|Y|6|M|8|1C|9|@]|A|@]|B|$N|O]]|$2|Z|4|-4|6|7|8|1D|9|@]|A|@]|B|$]]]]

if answer from @johnny didn't work, when you type the commands

<code>adb reverse tcp:8081 tcp:8081</code>
 <code>adb forward tcp:8082 tcp:8082</code>

and you get the following message

<pre><code>adb server is out of date. killing...
* daemon started successfully *
</code></pre>

that means that the adb command you are using in command line, and the adb tool used by the emulator are different.

you can confirm that by checking the location of adb (here I have two different tools in /usr/bin and /home, which are not symlinks as verified after)

<pre><code>42:~/pathToMyApp$ whereis adb
adb: /usr/bin/adb /home/42/Android/Sdk/platform-tools/adb /usr/share/man/man1/adb.1.gz
</code></pre>

I tried with the full path on both tools, and I discovered the emulator was using the adb tool in /home/...
So to make it work I now type

<pre><code>/home/42/Android/Sdk/platform-tools/adb reverse tcp:8081 tcp:8081;
/home/42/Android/Sdk/platform-tools/adb forward tcp:8082 tcp:8082
</code></pre>

entityMap|blocks|key|1f36q|text|我能够在我的pixel_3XL模拟器android+API级别解决这个问题:+29|type|unstyled|depth|inlineStyleRanges|entityRanges|data|48jjd|重置platform-tools的路径将我的路径更改为platform-tools|a3dcc|$+export+PATH=${PATH}:/root/Android/Sdk/platform-tools

$+adb+kill-server
$+adb+root++++++++++++++++++++++#will+give+root+access+for+adb

$+adb+forward+tcp:8082+tcp:8082+
$+adb+reverse+tcp:8081+tcp:8081

$+react-native+run-android++++++#restart+the+server+with+a+debugger+enabled|code-block|syntax|javascript|fmaf7|瞧，它在我的机器上起作用了..。祝你好运。|2gt02|此外，尝试在应用程序的开发人员菜单中将ip更改为127.0.0.1并手动更改端口->调试设置->调试服务器主机和端口|1i3p^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|O|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|P|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|Q|9|@]|A|@]|B|$H|I]]|$2|J|4|K|6|7|8|R|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|S|9|@]|A|@]|B|$]]|$2|N|4|-4|6|7|8|T|9|@]|A|@]|B|$]]]]

I was able to resolve this issue in my pixel_3XL simulator android API level : 29

reset the path for platform-tools
changed my PATH to platform-tools

<pre><code>$ export PATH=${PATH}:/root/Android/Sdk/platform-tools

$ adb kill-server
$ adb root #will give root access for adb

$ adb forward tcp:8082 tcp:8082 
$ adb reverse tcp:8081 tcp:8081

$ react-native run-android #restart the server with a debugger enabled
</code></pre>

voila, it worked in my machine... good luck.

additionaly try changing the ip to 127.0.0.1 and port manually in app's Developer menu -> Dev settings -> Debug server host &amp; port

entityMap|blocks|key|1ab45|text|这样做对我很有效|type|unstyled|depth|inlineStyleRanges|entityRanges|data|30lr8|在终端上：|6bak0|adb+reverse+tcp:8081+tcp:8081
adb+forward+tcp:8082+tcp:8082
adb+forward+tcp:8083+tcp:8083|code-block|syntax|javascript|3i676^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|K|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|L|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|M|9|@]|A|@]|B|$H|I]]|$2|J|4|-4|6|7|8|N|9|@]|A|@]|B|$]]]]

Doing this worked for me 

on terminal: 

<pre><code>adb reverse tcp:8081 tcp:8081
adb forward tcp:8082 tcp:8082
adb forward tcp:8083 tcp:8083
</code></pre>

Importing and using Realm on react native works fine for iOS. Android also works in terms of functionality, however, when using remote debugging on chrome the following error yields.

<a href="https://i.stack.imgur.com/p3vGK.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/p3vGK.png" alt="enter image description here"></a>

I've looked around almost everywhere and nobody seems to have a clear cut answer for this. Anyone here that has managed to get out of this pit? Remote debugging is quite essential as the app is dealing with rather complex objects and using <code>react-native log-ios</code> is a little hard on the workflow.

Thanks all.

Using Realm and Remote Debugging fails on android

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

 在react本机上导入和使用Realm可以很好地用于iOS。Android也在功能方面工作，然而，当在chrome上使用远程调试时，会产生以下错误。 ​ ? ​ 我几乎环顾了所有地方，似乎没有人对此有明确的答案。这里有没有人逃出了这个坑？远程调试是非常必要的，因为应用程序正在处理相当复杂的对象，并且在工作流程中使用react-native log-ios有点困难。 谢谢大家。 

问在android上使用领域和远程调试失败
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在android上使用领域和远程调试失败EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在android上使用领域和远程调试失败
EN