Block Accrescent in RethinkDNS

Oct 13, 2025 by talynt.org 47 views

Introduction

In this article, we will be discussing a bug that occurs when using RethinkDNS to block Accrescent, resulting in an app crash when trying to download a file. We will go over the steps to reproduce the issue, relevant logs, and provide a detailed explanation of the problem.

Expected Behavior

When RethinkDNS blocks Accrescent, the expected behavior is for the app to display an error notification warning about network access. However, in this case, the app crashes instead of displaying the expected error notification.

Steps to Reproduce

To reproduce this issue, follow these steps:

Block Accrescent in RethinkDNS: Open RethinkDNS and block Accrescent. This will prevent the app from accessing the internet.
Try to download an app: Attempt to download a file or app from the Google Play Store or any other source.

Relevant Logs

The relevant logs for this issue are as follows:

Process: app.accrescent.client, PID: 10926
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:1
91)
        at java.net.SocketInputStream.read(SocketInputStream.java:1
43)
        at com.android.org.conscrypt.ConscryptEngineSocket$SSLInput
Stream.readFromSocket(ConscryptEngineSocket.java:994)
        at com.android.org.conscrypt.ConscryptEngineSocket$SSLInput
Stream.processDataFromSocket(ConscryptEngineSocket.java:958)
        at com.android.org.conscrypt.ConscryptEngineSocket$SSLInput
Stream.-$$Nest$mprocessDataFromSocket(Unknown Source:0)
        at com.android.org.conscrypt.ConscryptEngineSocket.doHandsh
ake(ConscryptEngineSocket.java:240)
        at com.android.org.conscrypt.ConscryptEngineSocket.startHan
dshake(ConscryptEngineSocket.java:222)
        at C4.l.g(Unknown Source:102)
        at C4.l.c(Unknown Source:138)
        at C4.f.a(Unknown Source:746)
        at C4.a.a(Unknown Source:55)
        at D4.f.b(Unknown Source:125)
        at A4.b.a(Unknown Source:987)
        at D4.f.b(Unknown Source:125)
        at D4.a.a(Unknown Source:493)
        at D4.f.b(Unknown Source:125)
        at D4.a.a(Unknown Source:144)
        at D4.f.b(Unknown Source:125)
        at C4.j.g(Unknown Source:89)
        at C4.j.e(Unknown Source:38)
        at x2.b.h(Unknown Source:96)
        at D2.s.p(Unknown Source:29)
        at D2.s.h(Unknown Source:12)
        at H3.E.l0(Unknown Source:4)
        at i4.z.B(Unknown Source:73)
        at D2.z.d(Unknown Source:12)
        at x2.b.g(Unknown Source:118)
        at L2.d.p(Unknown Source:34)
        at M3.a.r(Unknown Source:7)
        at i4.E.run(Unknown Source:112)
        at f3.c.run(Unknown Source:630)
        at p4.k.run(Unknown Source:2)
        at p4.a.run(Unknown Source:95)
        Suppressed: java.net.SocketException: Connection reset
                ... 33 more
        Suppressed: n4.g: [p0{Cancelling}@e4f7c81, Dispatchers.Main
.immediate]

Phone Details

The phone details for this issue are as follows:

Phone Model: Pixel 8
Operating System: GrapheneOS latest stable
App Version: 0.25.0

Analysis

The issue occurs when RethinkDNS blocks Accrescent, preventing the app from accessing the internet. The app attempts to download a file, but the connection is reset, resulting in a java.net.SocketException: Connection reset error. This error is suppressed by the app, but it still crashes.

The issue is likely caused by the app's inability to handle the connection reset error. The app's code is not designed to handle this specific error, resulting in a crash.

Conclusion

In conclusion, the bug occurs when using RethinkDNS to block Accrescent, resulting in an app crash when trying to download a file. The issue is caused by the app's inability to handle the connection reset error. To fix this issue, the app's code needs to be modified to handle this specific error.

Recommendations

To fix this issue, the following recommendations can be made:

Modify the app's code: Modify the app's code to handle the connection reset error. This can be done by adding a try-catch block to catch the java.net.SocketException: Connection reset error and handle it accordingly.
Add error handling: Add error handling to the app's code to handle other potential errors that may occur when downloading a file.
Test the app: Test the app thoroughly to ensure that it can handle the connection reset error and other potential errors.

Introduction

In our previous article, we discussed a bug that occurs when using RethinkDNS to block Accrescent, resulting in an app crash when trying to download a file. In this article, we will answer some frequently asked questions (FAQs) related to this issue.

Q: What is RethinkDNS?

A: RethinkDNS is a DNS-based network blocking tool that allows users to block specific domains or IP addresses on their device.

Q: What is Accrescent?

A: Accrescent is an app that allows users to download files from the internet.

Q: Why does the app crash when I block Accrescent in RethinkDNS?

A: The app crashes when you block Accrescent in RethinkDNS because the app is unable to handle the connection reset error that occurs when it tries to download a file.

Q: What is a connection reset error?

A: A connection reset error occurs when a connection to a server is terminated unexpectedly, resulting in a java.net.SocketException: Connection reset error.

Q: How can I fix the app crash issue?

A: To fix the app crash issue, you can modify the app's code to handle the connection reset error. This can be done by adding a try-catch block to catch the java.net.SocketException: Connection reset error and handle it accordingly.

Q: What are some other potential errors that may occur when downloading a file?

A: Some other potential errors that may occur when downloading a file include:

java.net.SocketTimeoutException: This error occurs when a socket operation times out.
java.net.UnknownHostException: This error occurs when the host is unknown.
java.net.ConnectException: This error occurs when a connection to the server cannot be established.

Q: How can I add error handling to the app's code?

A: To add error handling to the app's code, you can use try-catch blocks to catch specific errors and handle them accordingly. For example:

try {
    // Code that may throw an exception
} catch (java.net.SocketException e) {
    // Handle the connection reset error
} catch (java.net.SocketTimeoutException e) {
    // Handle the socket timeout error
} catch (java.net.UnknownHostException e) {
    // Handle the unknown host error
} catch (java.net.ConnectException e) {
    // Handle the connection error
}

Q: How can I test the app to ensure that it can handle the connection reset error and other potential errors?

A: To test the app, you can use a testing framework such as JUnit to write test cases that simulate the connection reset error and other potential errors. You can then run the test cases to ensure that the app handles the errors correctly.

Conclusion

In conclusion, the bug app crash with RethinkDNS network block is a complex issue that requires a thorough understanding of the app's code and the underlying network protocols. By following the recommendations outlined in this article, you can fix the issue and ensure that the app handles the connection reset error and other potential errors correctly.

Recommendations

To fix the issue, we recommend the following:

Modify the app's code: Modify the app's code to handle the connection reset error and other potential errors.
Add error handling: Add error handling to the app's code to handle specific errors and exceptions.
Test the app: Test the app thoroughly to ensure that it can handle the connection reset error and other potential errors.

By following these recommendations, you can fix the issue and ensure that the app handles the connection reset error and other potential errors correctly.