KV-store `getRecordPublicUrl()` works locally but not on the Apify Platform

[JJetmar]

Issue description

Calling getRecordPublicUrl works locally I get KS-store item url with signature that works as a public link. But calling it on the Platform will generate:
http://10.0.32.27:8010/v2/key-value-stores/.../records/KEY?signature=blablalba, which after a click ends up with infinite loading.

Code sample

const defaultKvStore = await Actor.apifyClient.keyValueStore(input.run.defaultKeyValueStoreId);
console.log(await defaultKvStore.getRecordPublicUrl('INVALID_ITEMS'));

Package version

^3.4.4

Node.js version

22

Operating system

Linux

Actor or run link

KV: j79IgRSBva28eMqYZ check MESSAGE item

I have tested this on the next release

^3.4.5-beta.38

Other context

No response

[tobice]

Root cause: When running in Worker, the API URL is different so that Actors can talk directly to our API pods instead of going through the internet. Unfortunately, this breaks our resource public URL generation.

Discussed solution: Fix this on the Apify client.

• If isAtHome, ignore the provided baseUrl and instead use the canonical API URL provided in env variable APIFY_API_PUBLIC_BASE_URL.
• The sync KeyValueStore.getPublicUrl method in SDK already works this way -> we simply want to duplicate the solution.
• This needs to be fixed in all client methods that generate signed URLs.

@B4nan WDYT? Is this okay with you guys?

[tobice]

@barjin Started working on this, only to realize that you already have a solution 😅

I assigned this ticket to you 👍

[barjin]

Sorry about that, reviews ofc welcome :)

apify/apify-client-js#745

[barjin]

Closed by apify/apify-client-js#745