-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clip stopped working until I powered my iPhone off and on #9
Comments
You should also be able to open the app at anytime in order to restart the background process that powers the notification asking if you want your new copy to be saved to Clip. |
That hadn’t worked which is why I resorted to rebooting 😬 |
Interesting. That must mean the background process was hanging. I bet a force close of Clip and re-open would have got it going again, but a reboot would work too. Thanks for letting us know about this. |
I’m getting a haptic response when I select and then Copy but no notification and nothing is copied to the Clip app. I’ve killed the Clip app and restarted it several times. I bet if I reboot my phone it will work ok then |
@jefro108 It's possible that Clip notifications keep getting turned off for some reason. The haptic feedback means the background monitor process is working. Odd that you're not getting the notification, but check your Notification Settings and let us know. |
@jefro108 I wonder if DND is preventing the notifications for you. Does this issue happen after awhile of using it and then you have to reboot every time? I'm thinking a re-install may be in order her. |
Yes turning DND off solves the problem! |
@jefro108 Until (if) we find a way to access the clipboard without needing the notification, we cannot display the notification if your DND is turned on. |
Ok, that’s useful to know 👍🏻 |
I noticed that Clip wasn’t offering to save anything copied to the clipboard. I hadn’t rebooted my phone for a while, probably not since Altstore had last renewed the App IDs. Rebooting got it working again!
The text was updated successfully, but these errors were encountered: