70b43r 4 Report post Posted January 30, 2016 (edited) Hello, cashly is crashing every time I try to download a PQ with germanic umlaut within its name. Unfortunatly, such PQ can only be created from bookmarks. I've created samles to reproduce the problem. They are attached. Bookmarks are public and could be views here (without umlaut) and here (with umlaut). Both should include PQ-name within filename. Regards Edit: [2016-01-31] Links to PQ's won't work 17182274_cach.lytest.zip 17182278_cach.lytestäöüßÄÖÜ.zip Edited January 31, 2016 by 70b43r Share this post Link to post Share on other sites
Nic Hubbard 645 Report post Posted January 31, 2016 Thank you for reporting this. We have been working hard to fix various issues with GPX files and PQ imports that have come up, so I am glad that you brought this one up. Will do some testing and report back. Thanks! Share this post Link to post Share on other sites
Nic Hubbard 645 Report post Posted February 1, 2016 I did some testing and created the PQ's with the germanic naming. It is working to import them with the germanic naming. What version of Cachly are you using? 1.0.3? Share this post Link to post Share on other sites
70b43r 4 Report post Posted February 2, 2016 Yes, I'm using Version 1.0.3. Have you tried to create a PQ from by bookmark list? If you create a PQ manually, you should get similar results as in the attached screenshot. This is an error from geocaching website reported here Share this post Link to post Share on other sites
Nic Hubbard 645 Report post Posted February 2, 2016 Yes, I'm using Version 1.0.3. Have you tried to create a PQ from by bookmark list? I had, but I did it again and finally got it to crash. Will look into the issue and report back here. Thanks! Share this post Link to post Share on other sites
Nic Hubbard 645 Report post Posted February 5, 2016 I have finally figured out the issue causing this and fixed it. Was a very tricky one to find, but it came down to the file name not getting read, so the Pocket Query was unzipped incorrectly. It has been tested and fixed now, so will be out in the 1.0.4 App Store version as well as our weekly betas. Share this post Link to post Share on other sites
70b43r 4 Report post Posted February 9, 2016 Great. Waiting for the update 1 Nic Hubbard reacted to this Share this post Link to post Share on other sites
70b43r 4 Report post Posted March 4, 2016 Received the update today. Works now. Great work. Could be marked as solved. 1 Nic Hubbard reacted to this Share this post Link to post Share on other sites
Nic Hubbard 645 Report post Posted March 6, 2016 Received the update today. Works now. Great work. Could be marked as solved. Glad it is working for you! Share this post Link to post Share on other sites
