I can't do an initial check out of of either of my two most-used repositories. It starts to check out but then the app crashes, screen goes blank and I am returned back to the iOS home screen.
I use these repos as document storage. There are a number of large files (scanned pdfs over 20Mb) and many files have long file names - I don't know if this is relevant to the problem. The smaller of my two repos is 500Mb and contains about 1000 files. This one fails after just a couple of minutes. When I go back into the app, it shows the repo, but in a partially checked-out state, and there's no way to resume the checkout (as there's no update option on the root repo item in the app, and not all of the next-level directories have been created)
If I subsequently try an Update on an incompletely checked out repo, I get an error:
Thanks for your report.
Could you check out after you reboot your device ?
It seems that iOS kills iRepoReader when it uses a certain memory on
the multi application environment of iOS4.
I will try to minimize the memory of iRepoEditor.
Hi I now have the same problem with a checked out repository.
And after updating to Version 1.7.7 I'am not able to checkout the same repository again…
Could you use the 'Cleanup' command in the checked out directory ?
It seems that some working files aren't deleted normally. Please check it :-)
what is the end of this diskussion?
Lost customer - it seems
-> "Cleanup" - Clock is runnig "Checking …" for a moment - then it interrupted
-> "Status" - Clock is runnig "Checking …" - but no result - Button "Stop" dosn't work
We bouht 10 lincens to start.
What is to do?
What are the frame contiditions of the App?
Is it maybe a problem with files like Thumbs.db?
> Is it maybe a problem with files like Thumbs.db?
I could export a 'Thumbs.db' file from my test subversion server using iRepoReader 1.8.0 now
Couldn't export 'Thumbs.db' files normally ?
Sometimes it workes, sometimes not.
After i deleted all 'Thumbs.db' files in the repository the update worked fine.
I don't want to test it.
To us it works with this work around.
Log in to post a comment.