Jump to content

skiphunt

Members
  • Content count

    191
  • Joined

  • Last visited

About skiphunt

  • Rank
    Advanced Member

Recent Profile Visitors

712 profile views
  1. skiphunt

    Crashing when using Line Spacing

    It crashed like when adjusting line spacing on most of the other 8 images that I also cut/pasted that text block onto. So, it’s not likely a corrupt image. I was thinking maybe corrupt font, but if it crashed for you too, that rules that out. It was ONLY when adjusting line spacing every time. All other text edits worked fine.
  2. skiphunt

    Crashing when using Line Spacing

    can't do "quick screen recording" at the moment... I just tried again on a fresh image with fresh text and could not reproduce the crash. When I was having the problem a few days ago, I had some text that I was adding to several photos one-by-one. So, I copied the text layer, then pasted into the next photo to adjust font size, position, and line spacing. It crashed several times working with this original pasted text box. Although, I just tried again on a fresh image, dummy text, formatted text, then copy/pasted that text box layer onto a new photo and then adjusted line spacing. It did not crash. Then went back to one of my original images with text and tried to adjust the line spacing... and it DID crash out. I opened it again and tried, but it worked fine the second time. I'll attach the Photo doc lisbonNEWlowres.afphoto
  3. I'm consistently getting crashes when using the text line spacing in Photo. If I select one line then switch to spacing, eventually it works without crashing. It actually just crashes out of the session without saving the changes. It doesn't crash the whole app. iPad Pro 10.5 Photo 1.7.1 iOS 12.3.1
  4. I’m not going to argue with you again. The message was intended for Affinity support. Are you Affinity support? I installed the beta and used the app. All was fine until I installed the paid version. What ensued was 3 weeks of fumbling troubleshooting to find hidden files associated with the Affinity beta install. They had freakin “AffinityBeta” right in the file names. All of them. Removing them fixed my iCloud Drive. If I was able to find and remove them, Affinity certainly could’ve written an uninstaller that would’ve done that for me. I appreciate that you are a loyal fan of Affinity and feel compelled to appear combative to anyone who appears to be talking smack about your beloved, but Affinity needs to know when this BS happens so that maybe they can prevent it happening to others in the future. That’s all I’m doing. Sharing my findings and unpleasant user experience going from a public beta install to a paid install that shouldn’t have costed me 3 weeks of aggravation. I freaking paid for the app the second I could and installed it. I’m a big fan of Affinity too but they need to know the details of when a user experience goes all kinds of wrong.
  5. You’re wrong. On the desktop they could write an Uninstaller that removed them. Other applications have this. My iCloud Drive stopped working 3 weeks ago when I purchased Publisher and installed it while the beta was still installed. I had to spend countless hours in the dark grasping at straws and losing data to ultimately discover... what fixed it finally was removing over a half dozen leftover Publisher beta files that were hidden. I wouldn’t have had to waste all of that time troubleshooting this myself had Affinity offered an Uninstaller for the beta. Plain and simple.
  6. UPDATE: I'm posting these updates through this icloud drive nightmare here, because it's certainly related to the Affinity Publisher Beta. And, I thought I'd update my progress in case anyone else runs across this extremely aggravating scenario. This is the last time I think I'll ever participate in a public beta of any program. I think I'll leave it to those who don't mind the potential 3 week troubleshooting nightmare you might encounter. Anyway... I think I've finally figured out how to remove these last two stubborn and hidden Publisher folders (both iCloud related). I couldn't delete them, but I was able to move them to the desktop. Even after deleting them they'd reform themselves in the Mobile Documents folder (icloud drive data). So, I signed out of my Apple ID and finally ALL of my iCloud docs were saved. Before, only half of them would save before it would hang. Now it's working. After I was completely signed out and backed up. THEN, I moved the hidden Affinity Publisher icloud folders (one of them left over from the beta) to the desktop. Then I was able to delete and they appear to be finally gone. Before this, and what finally returned my iCloud to syncing and full functionality... was deleting a little over half a dozen hidden files related to the Publisher beta app that had already been deleted. The program "Funter" allowed me to find them all and ultimately get rid of them. It's free and finally saved the day: https://nektony.com I just got my Publisher reinstalled, all of my icloud drive reset up... have been syncing various files between OSX, iphone, ipad, etc. from Publisher, Designer, Photo and my other iCloud drive apps... I can't tell you how good it feels to FINALLY have this working and resolved again. This has taken up the better part of 3 weeks to resolve. Even though it was absolutely the Publisher Beta and updating to the public version before deleting the Beta that trashed my icloud drive, I know thats always a possibility when you agree to test beta software. What is particularly aggravating is how many hidden files from the beta that had caused the nightmare to begin with. I feel like Affinity should have created an Uninstall app that would have completely removed ALL parts of the app including all the scattered hidden ones... once the user was finished using the beta. I thought I'd deleted it all by deleting the visible files, but there were over a half dozen Publisher beta files (labeled publisher beta) that were hidden in various folders in the user library and not visible. I couldn't even find them using the key command to show hidden files. I was ONLY able to find all the culprits using the Funter app cited above. Had Affinity offered an uninstall app that would've removed all of the hidden problem files, it would have saved me 3 weeks of HELL and I wouldn't have lost any data. So, please Affinity... for future betas please ALSO create an absolute complete uninstall app too so that the user doesn't have to play guessing games for weeks trying to remove hidden system files that are corrupted or otherwise causing havoc.
  7. I'm posting these updates through this icloud drive nightmare here, because it's certainly related to the Affinity Publisher Beta. And, I thought I'd update my progress in case anyone else runs across this extremely aggravating scenario. This is the last time I think I'll ever participate in a public beta of any program. I think I'll leave it to those who don't mind the potential 3 week troubleshooting nightmare you might encounter. Anyway... I think I've finally figured out how to remove these last two stubborn and hidden Publisher folders (both iCloud related). I couldn't delete them, but I was able to move them to the desktop. Even after deleting them they'd reform themselves in the Mobile Documents folder (icloud drive data). So, I signed out of my Apple ID and finally ALL of my iCloud docs were saved. Before, only half of them would save before it would hang. Now it's working. After I was completely signed out and backed up. THEN, I moved the hidden Affinity Publisher icloud folders (one of them left over from the beta) to the desktop. Then I was able to delete and they appear to be finally gone. Before this, and what finally returned my iCloud to syncing and full functionality... was deleting a little over half a dozen hidden files related to the Publisher beta app that had already been deleted. The program "Funter" allowed me to find them all and ultimately get rid of them. It's free and finally saved the day: https://nektony.com
  8. I've got another long thread about how I initially thought the Affinity Publisher Beta might've screwed up my iCloud Drive based on it's iCloud Publisher folder saying "Beta"' on it even after I installed the purchased public version. Even after deleting the Beta version. The other thread outlines the nightmare I've been in ever since the launch day for Publisher. I've been trying everything I could find to fix it and have accidentally lost a lot of data in the process. Now... finally... I've got it working again. I used a program called Funter to find the hidden files. I deleted my public/purchased Publisher too in order to once again start over. When I used Funter to find any hidden files related to affinity publisher, it returned nearly a dozen hidden beta files. Some of them had to do with iCloud. I deleted almost all of them and what do you know? My iCloud Drive sync now works! So, it WAS the freakin' Publisher beta as I originally suspected. The only problem now is that Funter still shows 2 hidden affinity publisher folder files in the Mobile Docs folder. One says it's the affinitypublisherbeta icloud folder for "icloud beta). Both of them have to do with iCloud but I can't delete them. I get an Error -50 when I try. See attached images. Can anyone at Affinity, or anyone else... tell me how I can get rid of these last two hidden files? Some kind of forced delete? When I go directly to the Library/Mobile Documents folder and show hidden documents... I don't see the folders there. But Funter is showing they're indeed still there.
  9. Bad news... since I THOUGHT iCloud was now fixed... I made the mistake of re-enabling all of the Affinity iCloud stuff as well as my iAwrite app. Now it's not syncing again. Evidently had nothing to do with that Library file I removed. I'm giving up once and for all now. Going back to Dropbox. iCloud sync has cost me so my time of my life that I'll never get back. I have no clue if it's iCloud or Affinity, or iAwrite that's to blame. And now I don't really care. Back to Dropbox which works and maybe I'll revisit icloud again in a few months.
  10. Hmmm.... still getting the error when I try to access icloud drive folders via Safari web browser though. Dang it! Oh well... at least it's syncing now. I've already tried clearing Safari cache and history. No luck.
  11. Yeah, I already tried all of that... from every angle possible. I've been troubleshooting this for over 2 weeks. Trying everything I could find related to icloud sync and error problems. I'm not absolutely certain... but I may have found the corrupt file and I think I might have fixed it. After creating a Test User account and seeing that icloud appeared to be working as expected when logged into my Test User account... I started looking for possible corrupt user ID files. If this has indeed worked... it was pure luck that it was only the 5th or 6th plist file I tried to replace that fixed it "accountsd.plist" This file is located in Library/SyncedPreferences
  12. I don't want to be premature... but... I might've fixed it! I took a chance and started going through various Library plist files that might be related to my ID account. Deleted them, but saved a copy first. The first attempt killed my email accounts, but I got them back with the files I saved. There's one file that I removed and restarted that might've been the corrupt one. So far, my Pages test document in the Pages icloud drive folder appears to be syncing again from desktop to iOS and back to OSX. The culprit MIGHT have been "accountsd.plist" Fingers crossed, but looking good so far.
  13. @R C-R I did another test... Logged into the Test User account. Accessed my icloud drive via Safari. Opened a Pages document and made a test edit. Then, opened the edited Pages document via iCloud from my iPad. The edit showed up. Made another edit to the document via Pages on the iPad and quit out. I then logged out of the Test User desktop account and back into my normal user account. I opened the Pages document stored in the Pages icloud drive folder and both edits were there. I then made another edit to the Pages document via my normal account and saved. That edit didn't show up in the pages document, ie. it only doesn't work/sync when logged into my regular user account. When logged into the Test User account, it appears to work as expected, including full syncing both directions between IOS and OSX.
  14. Yes. I created a Test user account with admin permissions. I accessed it via Safari while logged into the Test user account and I didn't get the icloud drive error message. It's behaving as if it thinks I have more than one user ID, even though I only have the one. I've already tried changing my password twice.
  15. I appreciated it chief, but I've already done all of that countless times. I'm not new to the Apple OS. I've been using it for more than 25 years. I've troubleshooted my Macs and am called to troubleshoot other's machines too. Yes, I KNOW it's not a "drive". But icloud drive accessed via iOS is not consistent with the way my OSX machine is accessing. It's like they aren't connected. And YES, I only have one ID and password. I've also got an iTunes connect account for publishing... so this isn't my first rodeo. Though thanks for the info anyway.
×