Restructuring the codebase

[Urten]

This feels like a vertical mess. Have you planned on restructuring?

[TheDauntless]

Not yet. Since it's such a small tool, I don't really see the point, but PRs are welcome.

I personally only use this tool to pull and merge split-apks from a device, I never actually use the objection / patching functionality.

[Urten]

I can work on this on my free time -

What you think of this? -

patch-apk/
├── src/
│   └── patch_apk/
│       ├── __init__.py
│       ├── main.py              # Main entry point
│       ├── core/
│       │   ├── __init__.py
│       │   ├── apk_processor.py # APK processing logic
│       │   ├── apk_builder.py   # APK building/rebuilding
│       │   └── apk_signer.py    # APK signing logic
│       ├── utils/
│       │   ├── __init__.py 
│       │   ├── android.py       # Android-specific utilities
│       │   ├── file.py          # File operations
│       │   ├── xml.py          # XML processing utilities
│       │   └── cli.py          # CLI argument handling
│       └── config/
│           ├── __init__.py
│           └── constants.py     # Constants and configurations
├── tests/
│   └── ...
├── data/
│   └── patch-apk.keystore
├── requirements.txt
└── setup.py

[TheDauntless]

@Urten I had missed your comment and I was stuck on a long flight so I refactored the codebase. My focus was mostly on functional refactoring though. I've removed the dependency on objection as that introduced quite some issues, and your specific application caused issues due to multiple disassembly/assembly cycles. There's now only one cycle which will be a lot faster anyway. I wasn't able to test on Windows yet as I don't have a VM with me.

So feel free to still refactor, but first see if the dev branch works for you. The current refactor is maybe a bit rough, but it works :)

[Urten]

Hey i created a PR, can you check if its working for you?