Apps are not appearing when using ipfs companion

[jvluso]

The ui components of the most recent deployments were not included. This means that the content is not visible when using ipfs to render the ui. The result when running apm versions is

 ℹ voting.aragonpm.eth has 6 published versions
 ✔ 1.0.0: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:Qmer59t99nhZMk69TZTtXFn3im8uFLjpsLdub7zb75r1vq
 ✔ 1.0.1: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmPQjG4PSPXvhRYzxFBuU7HWSBTjyHL9HfRXapgjQUigkP
 ✔ 1.0.2: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmXkC9JfpR2xUEUYrGdcepjaBGPopd2cNJg2UKDpi8Hmye
 ✔ 1.0.3: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmctB78EiDW5LtSNA2FY8VUDwDWijv54UFDWKBs4a5nvyj
 ✔ 1.0.4: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmcwXZXdbxF5qgKFh66zfZHTXYoUeHT9gtVqn27WMCvxTr
 ✖ 1.0.5: 0xEae3502771635e6270e01f5B859DDB7ed780aebf Version not found in provider

[sohkai]

Hmm, which environment is this? On mainnet this should definitely be included (see tx) and it shows up for me:

~/Development/aragon/aragon-apps/apps/voting (master)

npx aragon apm versions --environment mainnet
 ℹ voting.aragonpm.eth has 6 published versions
 ✔ 1.0.0: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:Qmer59t99nhZMk69TZTtXFn3im8uFLjpsLdub7zb75r1vq
 ✔ 1.0.1: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmPQjG4PSPXvhRYzxFBuU7HWSBTjyHL9HfRXapgjQUigkP
 ✔ 1.0.2: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmXkC9JfpR2xUEUYrGdcepjaBGPopd2cNJg2UKDpi8Hmye
 ✔ 1.0.3: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmctB78EiDW5LtSNA2FY8VUDwDWijv54UFDWKBs4a5nvyj
 ✔ 1.0.4: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmcwXZXdbxF5qgKFh66zfZHTXYoUeHT9gtVqn27WMCvxTr
 ✔ 1.0.5: 0xEae3502771635e6270e01f5B859DDB7ed780aebf ipfs:QmTJ9ipNBoS91HZVmDU2yVoRJQqZ17DBXG82zdUETRvWc3

[jvluso]

This is on main net, though it is also happening on rinkeby. When I ran ipfs ls QmTJ9ipNBoS91HZVmDU2yVoRJQqZ17DBXG82zdUETRvWc3 it isn't giving a result. Do you know how widely it is pinned?

[sohkai]

Might be only on our IPFS node; it looks like other gateways don't have this cached. You can pin it yourself by decompressing the archives in this repo.

[sohkai]

Just wanted to check up on this @jvluso; did the hash end up resolving?

[jvluso]

It did, it just needed to be propagated a bit more.