Issues With The New Release V7
Posted on
Issues With The New Release V7 Average ratng: 6,7/10 4248 reviews
Problem:. The latest v6 releases broke backwards compatibility (semVersion) specifies patch changes should not break backwards compatibilities for the major version. In addition to not having a migration guide for v7, The latest v7 release fails to provide deprecation/rename mappings for new interface to help dev migrate without even reading a doc. Request: Can you provide a mapping/migration from v6 to v7? I was very confused at how to report user change?
![Release Release](https://i1.wp.com/www.mccarthyphotographic.com/wp-content/uploads/2018/02/MP_-2018-02-03_02.jpg?resize=640%2C357)
Given user one logs in after mParticle is started? Vs logout, then another logs in?
![Issues with the new release v75 Issues with the new release v75](https://confluence.atlassian.com/jirasoftware/files/946034808/947162509/7/1523756149785/fastkanban2.png)
![Issues Issues](https://www.backupassist.com/blog/wp-content/uploads/2013/04/7.0.1-700x328.png)
Issues With The New Release V7 Monitor
Are we supposed to keep a reference of options and update that object with a new identity request? What is the difference between MParticleUser vs MPIdentityApiRequest?