You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a contract live on mainnet that contains an entry point with type EntryPointType::Session.
We are testing migration from 1.5.6 to Condor. Other entry points seem to work correctly but this one fails with error Invalid context.
On EntryPointType::Caller description I can read: Previously installed 1.x stored session code should continue to work as the binary value matches. Since other methods are working, the binary doesn't seem to be the problem. Could you give any advice for troubleshooting?
Date Issue Began(optional)
25/07/2024
Attachments (optional)
No response
The text was updated successfully, but these errors were encountered:
I'm not sending any new wasm. The contract is installed on 1.5.6. The entry point can be called normally.
Then, I'm upgrading the network to 2.0.0. This entry point cannot be called successfully anymore.
Category
Request for Tech Support
Your email address
[email protected]
Project Name(Optional)
MAKE
Casper Network
Devnet
Priority
Medium
Node Functionality
Execution Engine
Description
We have a contract live on mainnet that contains an entry point with type
EntryPointType::Session
.We are testing migration from
1.5.6
toCondor
. Other entry points seem to work correctly but this one fails with errorInvalid context
.On
EntryPointType::Caller
description I can read:Previously installed 1.x stored session code should continue to work as the binary value matches
. Since other methods are working, the binary doesn't seem to be the problem. Could you give any advice for troubleshooting?Date Issue Began(optional)
25/07/2024
Attachments (optional)
No response
The text was updated successfully, but these errors were encountered: