# Ionic 2 RC.1 IOS Build device-ready not fired because of plugin problem?

**URL:** <https://forum.ionicframework.com/t/ionic-2-rc-1-ios-build-device-ready-not-fired-because-of-plugin-problem/67262>\
**Category:** ionic-v3\
**Created:** [October 17, 2016, 5:29pm UTC](https://forum.ionicframework.com/t/ionic-2-rc-1-ios-build-device-ready-not-fired-because-of-plugin-problem/67262 "2016-10-17T17:29:44Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![joshmorony](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/joshmorony/32/117695_2.png) [@joshmorony](https://forum.ionicframework.com/u/joshmorony)\
**Post date:** [November 1, 2016, 12:11am UTC](https://forum.ionicframework.com/t/ionic-2-rc-1-ios-build-device-ready-not-fired-because-of-plugin-problem/67262/9 "2016-11-01T00:11:57Z")

</div>

Definitely seems to be some kind of issue with CSP (not sure whether that’s an iOS10 bug or not), it looks like people are having success with this CSP though:

```auto
<meta http-equiv="Content-Security-Policy" content="default-src gap://ready file://* *; script-src 'self' 'unsafe-inline' 'unsafe-eval' *; style-src 'self' 'unsafe-inline' *”>

```

---

_[View the full topic](https://forum.ionicframework.com/t/ionic-2-rc-1-ios-build-device-ready-not-fired-because-of-plugin-problem/67262)._