You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a different bug from #7. That only crashes the apps, and can be fixed by checking if the status bar exists. This crashes the entire springboard, and has something to do with calling [vbar resetTimer] while the block from libobjcipc is still executing, or when the message is still being sent. I think.
Looking at the logs, it consistently crashes on the asynchronous libobjcipc message send from the presentVolumeBarWithView: method. I have more logs on my device and they're all almost identical. I'm not sure what I can do to resolve this.
Currently Tweak.xm needs the reply synchronously to init the volumebar object. Maybe in a replyHandler block in an async verison of sending ipc I can add the reply info to the volumebar, but I'd need to make sure that nothing in the tweak directly needs it immediately.
Looking at it, the tweak needs that stuff pretty immediately. I still see no reason why it's crashing, only that it has something to do with waiting on the async call and calling resetTimer
More info in issue #9, this commit closes that. When the volume buttons
were quickly pressed, the hook is still waiting on the async call to the
app but the second time calls resetTimer on the VolumeBar object.
resetTimer was incorrectly written, with one crucial part not inside the
check to make sure it was safe.
This is a different bug from #7. That only crashes the apps, and can be fixed by checking if the status bar exists. This crashes the entire springboard, and has something to do with calling [vbar resetTimer] while the block from libobjcipc is still executing, or when the message is still being sent. I think.
Logs:
The text was updated successfully, but these errors were encountered: