The next Kintone update after the May update is 7th June 2019. The release also includes the following updates.

• As App Actions will be available for the mobile version of Kintone on this update, the following related APIs will be added.
  • Relevant API:
    • Field Change Event (mobile) (mobile.app.record.create.change.(fieldcode))
  • Feature details:
    • On mobile, when an App Action is used, the field change event for the fields of the destination App listed in the field mapping settings will be triggered.

• The maximum file size of some of the files used for creating plug-ins will be raised.
  • Spec change details:
    • Of the files necessary for creating plug-ins, a number of them have been raised to accept a maximum file size of 20MB.
  • Before the update:
    • JavaScript files (for desktop, mobile, and the plug-in config page): 512KB
    • CSS files (for desktop and the plug-in config page): 512KB
    • Icon file: 512KB
  • After the update:
    • JavaScript files (for desktop, mobile, and the plug-in config page): 20MB
    • CSS files (for desktop and the plug-in config page): 20MB
    • Icon file: 20MB
• CSS files for mobile use can be set for plug-ins.
  • Spec change details:
    • CSS files for mobile use will be added to the files that can be used when creating plug-ins. It will be possible to develop plug-ins with CSS for mobile.
  • Before the update:
    • Cannot specify the mobile.css property in the manifest file (manifest.json).
  • After the update:
    • Can specify the mobile.css property in the manifest file (manifest.json).

• When using a User selection, Group selection, or Department selection field on mobile, setting the code for a user, group, or department that was not specified as a preset option in the field would not enter the user, group, or department into the selection field. This update fixes this bug.
  • Relevant APIs:
    • Onload Event (mobile) (mobile.app.record.create.show)
    • Save Event (mobile.app.record.create.submit)
    • Field Change Event (mobile.app.record.create.change.(fieldcode))
    • Onload Event (mobile) (mobile.app.record.edit.show)
    • Save Event (mobile.app.record.edit.submit)
    • Field Change Event (mobile.app.record.edit.change.(fieldcode))
    • Set Record Value (kintone.mobile.app.record.set)
  • Bug fix details: When setting the code of a user, group, or department in a User selection, Group selection, or Department selection field where that user, group, or department is not specified as a preset option:
    • Before the fix:
      • The user, group, or department is not added to the field
    • After the fix:
      • The user, group, or department is added to the field

• The API documents will be updated to state that on the desktop, when an App Action is used, the field change event for the fields of the destination App listed in the field mapping settings will be triggered.
  • Relevant API:
    • Field Change Event (desktop) (app.record.create.change.(fieldcode))
  • Update details:
    • On mobile, when an App Action is used, the field change event for the fields of the destination App listed in the field mapping settings will be triggered. This was how it always used to work, but it was not officially documented on this website.

With the addition of the ability to set CSS files for mobile use, the following API specs will be updated.

• A response parameter will be added to the Get Customization API.
  • Relevant API:
    • Get Customization (/k/v1/app/customize.json and /k/v1/preview/app/customize.json)
  • Spec change details:
    • The following property will be added to the response parameters:
      • mobile.css (An array listing data of CSS files for mobile)
• A new parameter will be added to the Update Customization API.
  • Relevant API:
    • Update Customization (/k/v1/app/customize.json and /k/v1/preview/app/customize.json)
  • Spec change details:
    • The following property can be updated:
      • mobile.css (An array listing data of CSS files for mobile)