Describe the bug:
It's not about the app but about issue #118
You closed the issue with "remote call doesn't support A15+ or M1-4. closed as this is a known issue.", but i succeeded to initialize and use remotecall on my ipad pro(gen 4), with M2 chip.
Actually most of my attempts failed but it succeeded when i try immediately after i reboot the device (two times in a row)
i'm sure it's functionable because i successfully disabled ota updates
To Reproduce:
Steps to reproduce the behavior:
- get a ipad pro(gen 4)
- reboot the device (may not be necessary)
- open lara
- init remotecall
Expected behavior:
Ummm...
idk
Screenshots:
Device Info:
- Device:
ipad pro (gen 4)
- Chip:
M2
- iOS Version:
26.0.1 23A355
- Jailbroken before?
no
- Lara version / commit:
a nightly release around May.15th
Logs:
lara.log
Additional context:
[Insert here]
Pre-submission checklist:
- [x ] I have searched existing issues (open and closed) and confirmed this is not a duplicate
- [x ] I can reproduce this on the latest version / commit of Lara
- [x ] I have provided sufficient detail (device info, logs, reproduction steps) for a maintainer to investigate
- [x ] I agree to communicate respectfully with the developers and understand that harassment may result in restricted support
Describe the bug:
It's not about the app but about issue #118
You closed the issue with "remote call doesn't support A15+ or M1-4. closed as this is a known issue.", but i succeeded to initialize and use remotecall on my ipad pro(gen 4), with M2 chip.
Actually most of my attempts failed but it succeeded when i try immediately after i reboot the device (two times in a row)
i'm sure it's functionable because i successfully disabled ota updates
To Reproduce:
Steps to reproduce the behavior:
Expected behavior:
Ummm...
idk
Screenshots:
Device Info:
ipad pro (gen 4)M226.0.1 23A355noa nightly release around May.15thLogs:
lara.log
Additional context:
[Insert here]Pre-submission checklist: