PI66177: CLI: WLAPPID IS NOT BEING SET IN MFPCLIENT.RESW FILES FOR WINDOWS PROJECTS

APAR status

• Closed as program error.

Error description

• Sometimes Windows applications are not able to connect to the
  server. This is due to the wlappid not being set in
  mfpclient.resw properties file. This value needs to be set
  during 'mfpdev app register' and should match the "assemblyName"
  that is used to register the application to the server.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users who register their Windows Universal apps using the    *
  * mfpdev CLI.                                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The `mfpdev app register` command was not properly           *
  * registering Windows Universal apps. The wrong assemblyName   *
  * was being used, so the app was registered with an            *
  * unrecognizable ID to the server. As a result, The app was    *
  * not able to ping the sever. The solution is to use the       *
  * assemblyName for the wlAppId in mfpclient.resw. The          *
  * assemblyName that is used is the application name without    *
  * the '.Windows' or '.WindowsPhone' appended to the end.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Install the updated mfpdev CLI and register the Windows
  Universal app.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MOBILE1ST PLATF

• Fixed component ID

  5725I4301

Applicable component levels

• R800 PSY

     UP