You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strict mode UntaggedSocketViolation issue is faced while making connection to segment.
Is it possible to tag this socket so that the policy violation isn't raised?
Stack trace:
D/StrictMode(17074): StrictMode policy violation: android.os.strictmode.UntaggedSocketViolation: Untagged socket detected; use TrafficStats.setTrafficStatsTag() to track all network usage
D/StrictMode(17074): at android.os.StrictMode.onUntaggedSocket(StrictMode.java:2251)
D/StrictMode(17074): at com.android.server.NetworkManagementSocketTagger.tag(NetworkManagementSocketTagger.java:82)
D/StrictMode(17074): at libcore.io.BlockGuardOs.tagSocket(BlockGuardOs.java:55)
D/StrictMode(17074): at libcore.io.BlockGuardOs.socket(BlockGuardOs.java:403)
D/StrictMode(17074): at libcore.io.ForwardingOs.socket(ForwardingOs.java:827)
D/StrictMode(17074): at libcore.io.IoBridge.socket(IoBridge.java:843)
D/StrictMode(17074): at java.net.PlainSocketImpl.socketCreate(PlainSocketImpl.java:128)
D/StrictMode(17074): at java.net.AbstractPlainSocketImpl.create(AbstractPlainSocketImpl.java:128)
D/StrictMode(17074): at java.net.Socket.createImpl(Socket.java:489)
D/StrictMode(17074): at java.net.Socket.getImpl(Socket.java:552)
D/StrictMode(17074): at java.net.Socket.setSoTimeout(Socket.java:1180)
D/StrictMode(17074): at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:143)
D/StrictMode(17074): at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
D/StrictMode(17074): at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
D/StrictMode(17074): at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
D/StrictMode(17074): at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
D/StrictMode(17074): at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
D/StrictMode(17074): at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
D/StrictMode(17074): at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
D/StrictMode(17074): at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:131)
D/StrictMode(17074): at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:262)
D/StrictMode(17074): at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getOutputStream(DelegatingHttpsURLConnection.java:219)
D/StrictMode(17074): at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:30)
D/StrictMode(17074): at com.segment.analytics.Client.createPostConnection(Client.java:50)
D/StrictMode(17074): at com.segment.analytics.Client.upload(Client.java:102)
D/StrictMode(17074): at com.segment.analytics.SegmentIntegration.performFlush(SegmentIntegration.java:383)
D/StrictMode(17074): at com.segment.analytics.SegmentIntegration$3.run(SegmentIntegration.java:361)
D/StrictMode(17074): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
D/StrictMode(17074): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
D/StrictMode(17074): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
D/StrictMode(17074): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
D/StrictMode(17074): at java.lang.Thread.run(Thread.java:920)
D/StrictMode(17074): at com.segment.analytics.internal.Utils$AnalyticsThread.run(Utils.java:641)
The text was updated successfully, but these errors were encountered:
Strict mode UntaggedSocketViolation issue is faced while making connection to segment.
Is it possible to tag this socket so that the policy violation isn't raised?
Stack trace:
The text was updated successfully, but these errors were encountered: