Failed to import custom slug from Bitly.

[TokuiNico]

Failed to import custom slug from Bitly.

[acelaya]

I can see there's a bug in the logic when reading custom slugs, because bitly seems to be still generating a random short code under the hood, and its API returns the custom slug in a different field.

However, this should not make the links to be skipped, but to be imported with that random short code instead of their custom slug (this is what I experienced while testing this).

Can you confirm what's the exact behavior you are experiencing? Did you explicitly see the "Skipped" keyword in the console for those, or did they get imported with an "unknown" random slug/short code?

[TokuiNico]

Thank you for your rapid assistance. I checked the shlink database and did find short URLs using random short codes.

I expected that in this situation, shlink would use a custom slug instead of the random code generated by bitly, or provide an option for me to decide which slug to use. This way, I can fully migrate my bitly short URL service to shlink.

[acelaya]

I expected that in this situation, shlink would use a custom slug instead of the random code generated by bitly

Yes, that's the intended behavior. I'll get that fixed.

[acelaya]

Shlink 4.1.0 has just been released, which includes this fix.

[TokuiNico]

Thanks for your help!