Can you give me a contact email?

[wlynxg]

No description provided.

[neilyoung]

foreverneilyoung at googlemail dot com

[neilyoung]

Why did you ask?

[wlynxg]

Why did you ask?

I took a look at calling net.ListenUnix on Android, and there was indeed a permission problem. I looked at the Android code and found that LocalSocket and LocalServerSocket can be created in the Android SDK. What I want from your email is that if there is any progress, I will let you know via email so that you don’t have to bother other people by replying to previous issues.

[neilyoung]

OK, thanks. I'm available. Indeed, LocalSocket is obtainable under Android w/o further permissions. I just added INTERNET

[neilyoung]

But again: This problem is most likely not caused by my net.Listen, but by a lot of other calls to net, issued from the LiveKit SDK

[neilyoung]

For instance the failing call to "set answer" ends finally in the PION WebRTC SDK, which uses net calls...

[neilyoung]

Do you think there will be a progress in this matter soon? I'm about to abandon go and gomobile at all. Looks like dead beef.

[wlynxg]

Do you think there will be a progress in this matter soon? I'm about to abandon go and gomobile at all. Looks like dead beef.

I feel that if you must use unix socket, it is better to use c which is more convenient. You can also use cgo. If you just want a local network you can create a localhost socket and this will work

[neilyoung]

I'm sorry, but you did misunderstand this case. The problem is in GOMOMBILE or GO, sure, but it is not UnixSocket. This works. I can open the socket, the GO module can listen to it, I can communicate with the GO module. 100% in Python, 100 % in Android <= 10, not on Android > 10 in due to this permission thing.

A couple of days ago I opened a discussion in PION SDK, which might better explain the problem I have.

pion/webrtc#2636

[neilyoung]

Happy New Year, just to let you know: Your GOLANG PR w.r.t. Android 11 permission seems to work. Discussion here pion/webrtc#2640 (comment) When do you think will they except that PR? TIA

…

Am 20.12.2023 um 02:57 schrieb the harder the luckier ***@***.***>: Do you think there will be a progress in this matter soon? I'm about to abandon go and gomobile at all. Looks like dead beef. I feel that if you must use unix socket, it is better to use c which is more convenient. You can also use cgo. If you just want a local network you can create a localhost socket and this will work — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFSPDC6TR7CLYEGGG7M3Y3YKJAW5AVCNFSM6AAAAABAKWJDKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRTG4ZDQOJUGA>. You are receiving this because you commented.

[wlynxg]

Happy New Year To You,
I think go's advancement of gomobile is relatively slow, and to some extent I think gomobile may be difficult to fix this problem. Because this problem is strongly related to the Android version, this problem will only appear after Android 11, but the Android version can only be obtained through the Android interface.
On the other hand, if a new security policy appears in Android later, then go will need to add new policies. This kind of thing is difficult to control.