@Chandramouli.M let me answer your questions.

1. As per communication and passing data from/to module there is a JavaScript Bridge APIs shipped OOTB. It allows you to defined some native interface from the native module code, which is later accessible from the JavaScript so it can be called from Pega. The Swift API docs are included in the Custom Module DevKit package. There is also an article describing the setup of the two-way communication. It contains code samples that may be helpful in your scenario as they feature passing data from Pega to the native Swift code.

2. iOS app build artifacts served by mobile channel are currently exclusively IPA files. In iOS ecosystem IPA is not allowed to be installed on iOS Simulator. The recommended way of testing the module on simulator is to use Custom Module DevKit. 

3. There may be a couple of reasons for the described behavior related to provisioning and signing assets. I would recommend attaching the device you are using to a MacOS computer and launching the console to view the device logs. Once connected - please scan the code and look for failures in the logs. The install errors usually receive meaningful messages indicating the error cause. Even before connecting the device and examining the logs you may check whether the certificates are valid and not revoked. Also, please check what kind of profile do you use. Another possible cause here is that there is a development provisioning profile used and it does not include the device on which you are attempting to install the app.