Added new features:

1. Accept/Reject credential offer
2. View Proof Requests and Scan proof request
3. View requested attributes and available credentials
4. Reject proof request and Present Presentation

Signed-off-by: Arshdeep Singh arsh.binny@gmail.com

setAspectRatio 8:10 work as 7:10. is it bug?

Have you tried using ngrok address instead? Connecting to localhost may not always work. Also make sure you're cleaning up ~/.indy_client folder in case you want to update the hostname.

Hi, I have similiar problem on iOS and Android versions. Mediator is running http://localhost:5000/.well-known/agent-configuration link is working in browser. On emulators internet is also working on browsers. However, when app is sending http request to mediator I am getting : [0:] System.Net.Http.HttpRequestException: Network subsystem is down ---> System.Net.Sockets.SocketException: Network subsystem is down at System.Net.Http.ConnectHelper.ConnectAsync (System.String host, System.Int32 port, System.Threading.CancellationToken cancellationToken) [0x000c8]

hello.. any update please?

Problem Statement When accepting a Credential offer, the error The requested pool cannot be opened because it does not have an existing configuration is thrown on executing the below code

(CredentialRequestMessage credentialRequestMessage, CredentialRecord newCredentialRecord) = await credentialService.CreateRequestAsync(agentContext, Credential.Record.Id);

On investigating, I found that the PoolConfigurator gets an exception (An IO error occurred). Below is the stack trace

at Hyperledger.Aries.Ledger.DefaultPoolService.CreatePoolAsync (System.String poolName, System.String genesisFile) [0x0002d] in D:\a\1\s\src\Hyperledger.Aries\Ledger\DefaultPoolService.cs:59 at SSI.Services.PoolConfigurator.ConfigurePoolsAsync () [0x0023b] in /Users/sahil.khanna/Documents/VisualStudio_Workspace/ssi-mobile-app/SSI/Services/PoolConfigurator.cs:54

Note

• The above scenario works fine on iOS. The problem is on an Android emulator and a device.
• The READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permissions are granted

Describe the bug

I have the following setup

• Xamarin Forms app for iOS
• DotNet mediator
• ACA-Py Agent

The connection between the mobile app and the ACA-Py agent is established and active. The ACA-Py agent wants to issue a credential to the Mobile agent. Below are the steps being followed.

1. ACA-Py sends a credential offer to the Mobile agent
2. The state of the credential in ACA-Py is offer_sent
3. The mobile agent gets the offer with the state Offered
4. The Mobile agent invokes the below method credentialService.CreateRequestAsync
5. The state of the credential in the Mobile agent is changed from Offered to Requested
6. The state of the credential in the ACA-Py agent remains offer_sent

Issue

The state of the credential in the ACA-Py agent should change from offer_sent to request_received (after step 5), however, it doesn't change.

This seems to work fine when two ACA-Py agents exchange credentials with each other

Steps To Reproduce

Given in the description

Screenshots

NA

Desktop (please complete the following information):

• OS: iOS, Mac
• .NET Core SDK 5.0.100-rc.2.20479.15
• Smartphone (please complete the following information):
  • Device: iOS Simulator
  • OS: iOS 14.1

Additional context

NA

This works fine if the below order if followed

• (CredentialRequestMessage credentialRequestMessage, CredentialRecord credentialRecord) = await credentialService.CreateRequestAsync(agentContext, credential.Id);
• await messageService.SendAsync(agentContext.Wallet, credentialRequestMessage, myConnection);

Hi,

When i am trying to click the "Create Wallet" button, "failed create wallet" popup message occur. so that i trying to debug and find the reason, in that i am getting "Connection refused" exception in "RegisterViewModel-> CreateWalletCommant->await _provisioningService.ProvisionAsync();" method. Line number 46 i am getting "Connection Refused" exception and i cannot able to move the next page. Can you give the solution for this?

Hi,

I have implemented a new screen to manage proofs. When i send my proof presentation, i received this error

Hyperledger.Indy.InvalidStructureException Message=A value being processed is not valid.

The error is thrown by this method "indy_prover_create_proof" in libindy. Any idea?

Describe the bug

I have the following setup

• Xamarin Forms app for iOS
• DotNet mediator
• ACA-Py Agent

The connection between the mobile app and the ACA-Py agent is established and active. The ACA-Py agent wants to issue a credential to the Mobile agent. Below are the steps being followed.

1. ACA-Py sends a credential offer to the Mobile agent
2. The state of the credential in ACA-Py is offer_sent
3. The mobile agent gets the offer with the state Offered
4. The Mobile agent invokes the below method credentialService.CreateRequestAsync
5. The state of the credential in the Mobile agent is changed from Offered to Requested
6. The state of the credential in the AcaPy agent remains offer_sent

Issue

The state of the credential in the ACA-Py agent should change from offer_sent to request_received (after step 5), however, it doesn't change

To Reproduce

Given in the description

Screenshots

NA

Desktop (please complete the following information):

• OS: iOS, Mac
• .NET Core SDK 5.0.100-rc.2.20479.15
• Smartphone (please complete the following information):
  • Device: iOS Simulator
  • OS: iOS 14.1

Additional context

NA

This PR just adds a label to the connection request. The label is mandatory to connect with acapy agents with the toolbox agent (and probably others) otherwise the acapy agent fails with a validation error "Label must not be null" as mentioned in #13

Glad you solved this. It's unfortunate that there's no one way that works for everyone. Libindy has too many external dependencies and this has been a point of great friction.

Finally, the issue has been fixed by adding environment variable targeting to indy sdk build.

export LIBRARY_PATH=$HOME/indy-sdk/libindy/target/debug export LD_LIBRARY_PATH=$LIBRARY_PATH export DYLD_LIBRARY_PATH=$LIBRARY_PATH export PATH=$PATH:$LIBRARY_PATH:$LD_LIBRARY_PATH:$DYLD_LIBRARY_PATH

Note: I have not placed libindy.dylib anywhere. Just followed the instruction to build from the source https://github.com/hyperledger/indy-sdk/blob/master/docs/build-guides/mac-build.md and then add the above environment variable as shown above in .zshrc file

Try removing wallet, to start mediator afresh. cd $HOME/.indy_client rm -rf wallet

I downloaded the static library from https://github.com/hyperledger/indy-sdk#macos and even try to build from the source https://github.com/hyperledger/indy-sdk/blob/master/docs/build-guides/mac-build.md but nothing works out.

@spsingh559 Did you download the library or built it yourself?

I have also the same issue.

dotnet info:

.NET Core SDK (reflecting any global.json): Version: 3.1.403 Commit: 9e895200cd

Runtime Environment: OS Name: Mac OS X OS Version: 10.15 OS Platform: Darwin RID: osx.10.15-x64 Base Path: /usr/local/share/dotnet/sdk/3.1.403/

Host (useful for support): Version: 3.1.9 Commit: 774fc3d6a9

.NET Core SDKs installed: 3.1.403 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed: Microsoft.AspNetCore.App 3.1.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.1.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

I have places the libindy.dylib file in Debug as well as netcoreapp3.1, but the error is the same.

what could be the possible solution?

Could this have been a temporary issue? The link points to the Hyperledger account on Bintray. You shouldn't be getting this warning. I can't seem to reproduce it.

The download link mentioned in https://github.com/hyperledger/aries-mobileagent-xamarin/tree/master/libs README.md file shown as a fake or suspicious link

Though we can ignore the warning, it should be better to place or host in a much better way. Link: https://hyperledger-org.bintray.com/aries/

yeah I need it too ! setCropInfo() function

I had the same issue. AVD cannot reach to http://localhost:5000 address (as expected?). Using 10.0.2.2 instead of localhost can access to http://10.0.2.2:5000/.well-known/agent-configuration. However, the mediator agent configuration returns localhost as the ServiceEndpoint; although EndPointUri option is configured with 10.0.2.2 as follows in the mediator:

options.EndpointUri = "http://10.0.2.2:5000";

Here is the response that the mobile agent gets from http://10.0.2.2:5000/.well-known/agent-configuration

{"ServiceEndpoint":"http://localhost:5000","RoutingKey":"6JqWGVshN83z2iekNitpz5CVkPhqBTtYgyN5V59ChnAm","Invitation":{"label":null,"imageUrl":null,"serviceEndpoint":"http://localhost:5000","routingKeys":null,"recipientKeys":["4b8cii9VfYc15yRmAekocgPqUm3sEqJvNCFT714YSBgJ"],"@id":"b51f3a9d-c077-4e9c-a338-c4307bb2b2a3","@type":"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/connections/1.0/invitation"}}

Therefore, mobile agent cannot continue the wallet creation process.