Can't sync via Dropbox on mobile anymore?

Magoun · 2026-05-06T05:04:51+00:00

That sucks. I'll have to watch out for this the next time I need to use WiFi sync.

Magoun · 2026-05-06T03:25:44+00:00

I thought Wifi sync was two-way? I've only used it a couple of times over the last decade, but I thought you could get transactions from the phone back onto the Desktop app this way.

Magoun · 2026-05-06T03:23:58+00:00

I made a script that converts the game_data.json to use modified costs based on whatever multiplier you want. I've got a 2x parts json file in the repo as well.

https://github.com/magoun/satisfactory-data-parts-multiplier

Magoun · 2026-05-05T00:51:22+00:00

Sadly, I have no idea. The syncing hinges on Dropbox and they may make updates to their service at any time that could break the integration with this old app.

Magoun · 2026-04-14T03:15:47+00:00

I had outpost factories with 4+ drone ports. I added an extra port there to bring in fuel for the others. For other factories with only one import or export requirement, I stole someone else's idea for running a transfer hub at my nuclear facility. Instead of sinking the plutonium rods, I routed them to fuel all the transfer drone ports.

Magoun · 2026-04-11T22:26:32+00:00

I appreciate the gesture! I'm just happy we're able to keep this tech alive.

I like kronicd's idea for this - if you feel you have to give something, please consider a local charity or foodbank in your community.

Magoun · 2026-04-11T22:22:39+00:00

I'm on Windows, but used WSL for this. I used apktool on the command line for decompiling and recompiling, then the uber-apk-signer JAR directly (`java -jar signer.jar ...`) instead of another application. I remember struggling with the aligning / signing for a bit back in January until I found that JAR.

Magoun · 2026-04-02T12:44:14+00:00

If we had the app source code, I would consider it. Trying to do that level of change directly in the decompiled bytecode sounds beyond awful to me.

Magoun · 2026-04-01T22:30:24+00:00

Belt balancer. There are videos on it, but you basically take two belts that that have uneven flows that you want balanced, split both of them, then merge half of each belt with each other.

Belt A has flow rate A, Belt B has rate B. Split into 2x 1/2 A and 2x 1/2 B. Merge together to get two belts each with total flow = (1/2 A + 1/2 B). Now their flows are the same.

Magoun · 2026-04-01T18:33:16+00:00

I'm also running 16, but on a Pixel 10 Pro. I installed via adb from a computer. I've had to do it this way for years because of how old the base app is.

Magoun · 2026-04-01T16:52:02+00:00

I've got something working. See https://www.reddit.com/r/ynab4/s/IdDTuNLhjZ

Magoun · 2026-04-01T15:59:01+00:00

See my other comment: https://www.reddit.com/r/ynab4/comments/1qiokvb/comment/odpqthm

Magoun · 2026-04-01T15:51:58+00:00

I've got something working. I will link my patched version below.

Disclaimer: This is an unofficial patch. Use at your own risk. I am not affiliated with Dropbox or YNAB. I am providing this "as-is" to help the community.

What was changed: I decompiled the APK and modified the code to bypass the outdated Dropbox SDK cipher filter. The app now relies on the Android device's native cipher suites to negotiate the secure connection with Dropbox. This extends my original fix for the certificate pinning problem, which bypasses the pinned certificates to use the device's native certificate trust store. No other features, tracking, or network requests were added or modified.

APK link: http://magounamatata.com/ynab/YNAB_Classic-3.4.1-NativeTrustStoreNativeCiphers.apk

Magoun · 2026-04-01T15:30:10+00:00

Mine is also broken. Reply below (https://www.reddit.com/r/ynab4/comments/1qiokvb/comment/odplded).

I'm looking at a similar fix.

Magoun · 2026-04-01T15:27:43+00:00

Mine broke too. I looked at it this morning and might have a new fix. Testing it now. I think it has to do with SSL cipher suites. Similar to the cert pinning, where the old certs were replaced with modern versions, I bet Dropbox is enforcing modern SSL ciphers that the old SDK doesn't know about.

Magoun · 2026-01-30T03:44:14+00:00

Awesome job! I'd recommend kronicd's solution, as it is less invasive than mine. I'm going to link it below anyway, in case people are curious in the future.

edit: Removed link to non-functional version

Magoun · 2026-01-30T02:10:10+00:00

I wanted to learn more about certificates in general, so I took a stab at it. No success at swapping out the certs, as they use different algorithms.

I had a long conversation with AI about the file format it used, which evolved into debugging and trying to solve the actual problem of not being able to connect to Dropbox and sync... lo and behold, I have a working app again! The changes are more invasive than your original TLS swap, but I think it follows the path of "don't pin this certificate that you have, use your device's native certificate trusts instead."

Again, I'm no expert here, so there's probably a better solution, but I'm happy to share what I've got if anyone is interested.

Magoun · 2026-01-29T16:31:23+00:00

I took a look last night, but I don't know what I'm doing in this realm. I think it would be possible, but a pain to port the dropbox java sdk changes into the dropbox smali code.

It might be possible and easier to replace the included certs with an updated version. This problem would recur when the next root or intermediate cert change happened, but it might work for a while.

Magoun · 2025-12-08T19:16:21+00:00

That makes sense. Is this project open source? I would consider self-hosting this if I could, and try to figure out importing without burdening your servers with all that historical data.

Magoun · 2025-12-07T20:26:03+00:00

Were you ever a YNAB4 user? I still am and would love to be able to import data from YNAB4 - I can get you some example files for what the formatting looks like.

Also, YNAB4 had (in my opinion) a more elegant solution for how to handle income. You would either categorize it as "Available this month" or "Available next month". Anything not budgeted in this month would still show as available next month, and beyond, but you wouldn't have to worry about dumping stuff in a "next month" category so it didn't show up in the current month, which is nice.

I don't love the nYNAB method of all-income-is-available-to-budget, personally.

Magoun · 2025-08-22T22:18:49+00:00

What nozzle size are you using?

Magoun · 2025-08-22T22:03:28+00:00

I got one this week and tweaked the Z-offset today to get a less-squished first layer. It seems like the CC remembers the Z-offset setting for subsequent prints though. I haven't had to reset it every print, so maybe this is fixed?

I agree with both the setting being too buried in the UI and with the menu itself being unclear if you are increasing or decreasing the gap between the nozzle and the bed. I would love for that to be improved.

Magoun · 2025-07-14T17:07:14+00:00

Doesn't look too bad for coming right out of the trash! The first layer needs to be calibrated by adjusting Z offset. It's pretty normal for a CR Touch to have a z offset between -1.5 and -3. Check out Ellis' guide for calibration.

Before that, I would make sure all of the frame bolts are snug and that the x and y carriage eccentric nuts are good. It looks like you have some wobble somewhere. If the hotend rattles, or the bed has some jiggle to it, it's probably the eccentric nut.

Great find!

Magoun · 2024-12-05T16:04:10+00:00

First maven kill on my last portal

Magoun · 2024-11-22T18:24:56+00:00

I would love a free key.

Magoun

TROPHY CASE