I would add similar thoughts to @rancor13, our field work has suggested otherwise that something within DD is preventing us from flying within the DJI Geofenced areas. We were recently flying near an airport mapping some riparian areas, and one of our flight plans clipped an authorization area of DJIs. I would suggest several following features.
in mission planning, these geofenced areas should be shown, and the user notified if a flight plan clips an area. This currently does not happen for us. i would call this a mission critical feature, as we are sometimes driving multiple hours to our sites, and to find out that an application doesn't work is a liability we cannot afford.
We had already unlocked the P4 using the DJI process, and had permission and permits from both the FAA as well as ATC for the airport. Finding out after they had shut down the runways for us to fly that your application prevented us from doing our job was, well, not good.
If DD hasn't added anything to prevent us from flying, then you need to review the SDK and see what is stopping us. Perhaps a pre-existing feature is now fighting the DJI SDK.
Also, @chasemgray, your own website contradicts your statement. See the text below.
"No Fly Zones will be respected in the DroneDeploy app: Because the DJI platform for developers will not allow automated flights in No Fly Zones, our app WILL NOT allow you to fly within No Fly Zones, even if you have an exception from the relevant government parties in the area." taken from the following page.