chore(deps): bump org.fossify:android-smsmms from c3e678befd to 5.2.5

[dependabot]

Bumps org.fossify:android-smsmms from c3e678befd to 5.2.5.

Release notes

Sourced from org.fossify:android-smsmms's releases.

v5.2.5

No release notes provided.

v5.2.3

• Improvements around dual-sim support when sending messages
• Improvements for receiving MMS on Xiaomi devices and various carriers that require slightly different support
• Fix receiving MMS in the sample application

v5.2.0

• Save the original sent time #160
• Improve dual SIM support for downloading MMS #162

v5.1.2

Allow for overriding some of the StatusUpdateReceiver implementations.

v5.1.1

Previously, if a user disabled group MMS and tried to send an image to a group of people, it would still be sent out as a group MMS. This bug has been fixed.

v5.1.0

Adds: klinker41/android-smsmms#139

5.0.0

This release improves threading on the BroadcastReceivers. If you are implementing or overriding any of the behavior for receiving messages, updating the "sent" status on messages, learning when a message has been marked as delivered, etc, the APIs for these receivers have changed.

For example, if you wanted to update the sent status of a message in your own app's database (outside of the share SMS/MMS database on your phone, which the SentReceiver already does for your), you could make a receiver like this:

public class MySentReceiver extends SentReceiver {
@Override
public void onMessageStatusUpdated(Context context, Intent intent, int resultCode) {
    // your code to update the status of the message. It will be run in a background thread.
    switch (resultCode) {
        case Activity.RESULT_OK:
        ...
}

}

Basically, if you were overriding the onReceive method of the SentReceiver, MmsSentReceiver, or DeliveredReceiver, you will move that implementation to the onMessageStatusUpdated method instead.

Update to OkHttp 3.0

No release notes provided.

Crash fix for specific devices

From PR #96

Explicitly define "sent" and "delivered" broadcasts

You can now use the following methods to explicitly set up the "sent" and "delivered" broadcasts for SMS/MMS, instead of relying on the AndroidManifest entries:

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[naveensingh]

@dependabot ignore this dependency

[dependabot]

OK, I won't notify you about org.fossify:android-smsmms again, unless you re-open this PR.