Skip to content
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

send2cgeo - Stuck on multi cache import #6146

Closed
FSeixasPT opened this issue Nov 19, 2016 · 2 comments
Closed

send2cgeo - Stuck on multi cache import #6146

FSeixasPT opened this issue Nov 19, 2016 · 2 comments
Labels
Bug Issues classified as a bug Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility

Comments

@FSeixasPT
Copy link

Detailed steps causing the problem:
  • On my PC I added a bunch of caches to the "send2cgeo" import queue;
  • On my Android 6 phone I tried to import them to a list;
Actual behavior after performing these steps:
  • It imported a lot of caches correctly, but is now stuck on cache GC11CPZ - maybe it's related to its name starting with a "#"?
Expected behavior after performing these steps:
  • Every cache should be properly imported.
Version of c:geo used:

2016.11.05

Is the problem reproducible for you?

Yes

System information:

Browser: Chrome 54.0.2840.71 m (64-bit)
Extension: Tampermonkey 4.1.10 with Send to c:geo 0.37
Phone: Xiaomi Redmi 3S Prime running Android 6.0.1 MMB29M (MIUI 8 Global 6.9.8 Beta)

@Lineflyer Lineflyer added Bug Issues classified as a bug Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility labels Nov 20, 2016
@Lineflyer
Copy link
Member

I could not find any problem while trying to reproduce this issue.
Also GC11CPZ was handled normally using send2cgeo.

@bockyPT
You are writing it is reproducible for you?! How many caches did you queue up in total? Did you start the import only after queueing the caches or in parallel to sending them?

Please be aware that importing depends on some external factors like network connection availability, website availability, which I would assume more likely to be the reason for such a problem.

@Lineflyer
Copy link
Member

Closing due to lack of feedback from submitter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues classified as a bug Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility
Projects
None yet
Development

No branches or pull requests

2 participants