Jump to content
You must now use your email address to sign in [click for more info] ×

Recommended Posts

I am not sure why but each time there has been a problem I've looked for data and there has not been any.  Anyone seeing the same thing?   I am having trouble with the cloning tool but all I can do is describe it with words or screen capture.  The tool either generates a crash or a simple closing of the app.  This problem is not random but continuous.  

iPad Pro 1T

latest iOS 12, not the beta

Edited by p_mac
Link to comment
Share on other sites

On mine they are named as follows: Photo iPad-2019-06-30-190616.ips.beta

M1 IPad Air 10.9/256GB   lpadOS 17.1.1 Apple Pencil (2nd gen).
Affinity Photo 1.10.5 Affinity Design 1.10.5 
Affinity Publisher 2, Affinity Designer 2, Affinity Photo 2 and betas.

Official Online iPad Help documents (multi-lingual) here: https://affinity.https://affinity.help/ 

 

Link to comment
Share on other sites

3 hours ago, p_mac said:

each time there has been a problem I've looked for data and there has not been any

I just reproduced your ‘Clone tool strange behaviour’ and easily found analytics data for it.

C39849E9-E226-4C7A-AEA3-46D81EC3F9E0.jpeg

Alfred spacer.png
Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro
Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.4.1 (iPad 7th gen)

Link to comment
Share on other sites

Thanks DM1 and Alfred for your help.  I went back again and looked for Photo iPad but none had the dates that the crashed were happening.   

Sent all the data to Apple and the Devs 

Reset my date and time manually.

Reset the iPad Pro 

‘Now I am getting the correct date and time as well as the crash reports.  Prior to this I was getting nothing as there were no current dates and times being recorded.   

The crashes with the clone tool seem to be very random   Sometimes it clones perfectly, then on the same image it crashes.   

Very strange behaviour   

 

 

 

 

Link to comment
Share on other sites

  • 8 months later...
  • Staff

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.