Feroze Shahpurwala

@wojtkowiak While developing each hot code push does cause the app to close and reopen. But I have not noticed the app crash and become unusable while developing. I just...

@wojtkowiak I just tried building with the -b option so you do not need to run meteor separately and it fails with the following error: ``` VERBOSE meteorApp: copying mobile...

@wojtkowiak Actually the issue above with using -b was the fault of my code. I fixed it and now it works using -b. But without -b you have to start...

I got it I had to change the code to: ``` var sideMenu = $(this.sideMenuContainer); sideMenu.removeData("mm"); sideMenu.metisMenu(); ```

Although it doesnt really work that well. I notice that the the navigation dropdown always stays open. And doesn't close. At least one stays open. When I refresh the page...

Ok so actually I figured out how to use @arlen43 solution but with the newest MetisMenu code ``` function Plugin(option) { return this.each(function() { var $this = $(this); var data...

find about line 250 in the code and compare this function with the original ``` javascript function Plugin(option) { return this.each(function() { var $this = $(this); var data = $this.data('mm');...

Just updated from 2.2.0 to 2.7.0 and the new fix for enabling metis menu to re-initialize with new data is the one that @SuricateCan mentioned. @onokumus any reason this hasn't...

Here is what worked for us. We actually develop on each app separately at first just by commenting out one package or the other. So if we work on mobile...

@davidmulligan I am having the exact same issue.